Skip to content

use gh runners in ci - #5019

Merged
mergify[bot] merged 1 commit into
mainfrom
use-gh-runners-ci
Aug 6, 2026
Merged

use gh runners in ci#5019
mergify[bot] merged 1 commit into
mainfrom
use-gh-runners-ci

Conversation

@Fraccaman

Copy link
Copy Markdown
Collaborator

Describe your changes

Checklist before merging

  • If this PR has some consensus breaking changes, I added the corresponding breaking:: labels
    • This will require 2 reviewers to approve the changes
  • If this PR requires changes to the docs or specs, a corresponding PR is opened in the namada-docs repo
    • Relevant PR if applies:
  • If this PR affects services such as namada-indexer or namada-masp-indexer, a corresponding PR is opened in that repo
    • Relevant PR if applies:

@github-actions github-actions Bot added the breaking:api public API breaking change label Aug 5, 2026
@Fraccaman
Fraccaman force-pushed the use-gh-runners-ci branch 7 times, most recently from d064f09 to aa8e53a Compare August 5, 2026 14:00
@Fraccaman
Fraccaman requested a review from sug0 August 5, 2026 14:00
@sug0
sug0 requested a lite review from Copilot August 5, 2026 16:27

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Human review recommended

It changes critical CI runner selection/caching infrastructure and also removes MSRV verification from PR checks without an evident replacement.

Pull request overview

This PR updates the project’s GitHub Actions configuration to use new runner labels / caching infrastructure and adjusts an IBC MASP-related E2E test timing to avoid shielding before conversions are published.

Changes:

  • Switch multiple CI and docker workflows to new namada-runners-* runners and update cache/role environment variables, including centralizing default RUSTFLAGS.
  • Extend the ibc_token_inflation E2E test wait period to include an additional MASP epoch, and update the expected runtime budget in e2e.json.
  • Remove the MSRV verification job from the PR workflow and apply a minor formatting-only change in release.yml.
File summaries
File Description
crates/tests/src/e2e/ibc_tests.rs Wait longer before shielding to ensure MASP conversions exist, preventing permanent “undated note” behavior from invalidating inflation checks.
.github/workflows/scripts/e2e.json Increase the scheduled budget for ibc_token_inflation to reflect the longer wait.
.github/workflows/release.yml Formatting-only adjustment (no functional change).
.github/workflows/pr.yml Removes the MSRV (cargo-msrv) job from PR checks.
.github/workflows/docker.yml Moves the docker workflow to the new runner label.
.github/workflows/ci.yml Migrates CI jobs to new runner labels and updates cache/role/env wiring; centralizes default RUSTFLAGS with targeted overrides.
Review details

Suppressed comments (1)

.github/workflows/pr.yml:89

  • The PR workflow no longer runs the MSRV verification job (cargo-msrv) and there doesn’t appear to be an equivalent check in other workflows; this reduces CI coverage for the project’s minimum supported Rust version and may allow MSRV regressions to merge unnoticed. If the intent is to disable it, consider adding an explicit rationale in the PR description and/or moving MSRV verification to another workflow (e.g., ci.yml or a scheduled workflow) rather than removing it entirely.
        uses: actions-ecosystem/action-add-labels@v1
        if: steps.semver.outcome == 'failure'
        with:
          labels: "breaking:api"

  • Files reviewed: 5/6 changed files
  • Comments generated: 0
  • Review effort level: Lite

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.

@sug0 sug0 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd also get rid of the changelog stuff in ci

@mergify

mergify Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Queued — the merge queue status continues in this comment ↓.

@mergify

mergify Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 38 minutes 48 seconds in the queue, including 37 minutes 39 seconds running CI.

Waiting for any of
  • check-neutral = test-e2e (1)
  • check-skipped = test-e2e (1)
  • check-success = test-e2e (1)
All conditions
  • any of [🛡 GitHub branch protection]:
    • check-neutral = test-e2e (1)
    • check-skipped = test-e2e (1)
    • check-success = test-e2e (1)
  • github-review-approved [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = test-e2e-with-device-automation
    • check-neutral = test-e2e-with-device-automation
    • check-skipped = test-e2e-with-device-automation
  • any of [🛡 GitHub branch protection]:
    • check-success = check-benchmarks
    • check-neutral = check-benchmarks
    • check-skipped = check-benchmarks
  • any of [🛡 GitHub branch protection]:
    • check-success = check-packages
    • check-neutral = check-packages
    • check-skipped = check-packages
  • any of [🛡 GitHub branch protection]:
    • check-success = build-binaries
    • check-neutral = build-binaries
    • check-skipped = build-binaries
  • any of [🛡 GitHub branch protection]:
    • check-success = build-wasm (wasm-for-tests, build-wasm-tests-scripts, wasm_for_tests/*.wasm)
    • check-neutral = build-wasm (wasm-for-tests, build-wasm-tests-scripts, wasm_for_tests/*.wasm)
    • check-skipped = build-wasm (wasm-for-tests, build-wasm-tests-scripts, wasm_for_tests/*.wasm)
  • any of [🛡 GitHub branch protection]:
    • check-success = lints
    • check-neutral = lints
    • check-skipped = lints
  • any of [🛡 GitHub branch protection]:
    • check-success = rust-docs
    • check-neutral = rust-docs
    • check-skipped = rust-docs
  • any of [🛡 GitHub branch protection]:
    • check-success = test-wasm
    • check-neutral = test-wasm
    • check-skipped = test-wasm
  • any of [🛡 GitHub branch protection]:
    • check-success = test-e2e (0)
    • check-neutral = test-e2e (0)
    • check-skipped = test-e2e (0)
  • any of [🛡 GitHub branch protection]:
    • check-success = test-e2e (2)
    • check-neutral = test-e2e (2)
    • check-skipped = test-e2e (2)
  • any of [🛡 GitHub branch protection]:
    • check-success = test-e2e (3)
    • check-neutral = test-e2e (3)
    • check-skipped = test-e2e (3)
  • any of [🛡 GitHub branch protection]:
    • check-success = test-e2e (4)
    • check-neutral = test-e2e (4)
    • check-skipped = test-e2e (4)
  • any of [🛡 GitHub branch protection]:
    • check-success = test-integration
    • check-neutral = test-integration
    • check-skipped = test-integration
  • any of [🛡 GitHub branch protection]:
    • check-success = test-unit
    • check-neutral = test-unit
    • check-skipped = test-unit
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections

Reason

The merge conditions cannot be satisfied due to failing checks

  • test-e2e-with-device-automation
  • check-benchmarks
  • check-packages
  • build-binaries
  • build-wasm (wasm-for-tests, build-wasm-tests-scripts, wasm_for_tests/*.wasm)
  • lints
  • rust-docs
  • test-wasm
  • test-e2e (0)
  • test-e2e (1)
  • test-e2e (2)
  • test-e2e (3)
  • test-e2e (4)
  • test-integration
  • test-unit
  • Mergify Merge Protections

Failing checks:

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

@codecov

codecov Bot commented Aug 5, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@mergify

mergify Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Hey @Fraccaman, your pull request has been dequeued due to the following reason: CHECKS_FAILED.
Sorry about that, but you can requeue the PR by using @mergifyio requeue if you think this was a mistake.

@mergify mergify Bot added dequeued and removed queued labels Aug 5, 2026
@mergify mergify Bot removed the dequeued label Aug 6, 2026
@Fraccaman

Copy link
Copy Markdown
Collaborator Author

@Mergifyio queue

@mergify

mergify Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 59 minutes 28 seconds in the queue, including 57 minutes 33 seconds running CI.

Required conditions to merge
  • github-review-approved [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = test-e2e-with-device-automation
    • check-neutral = test-e2e-with-device-automation
    • check-skipped = test-e2e-with-device-automation
  • any of [🛡 GitHub branch protection]:
    • check-success = check-benchmarks
    • check-neutral = check-benchmarks
    • check-skipped = check-benchmarks
  • any of [🛡 GitHub branch protection]:
    • check-success = check-packages
    • check-neutral = check-packages
    • check-skipped = check-packages
  • any of [🛡 GitHub branch protection]:
    • check-success = build-binaries
    • check-neutral = build-binaries
    • check-skipped = build-binaries
  • any of [🛡 GitHub branch protection]:
    • check-success = build-wasm (wasm-for-tests, build-wasm-tests-scripts, wasm_for_tests/*.wasm)
    • check-neutral = build-wasm (wasm-for-tests, build-wasm-tests-scripts, wasm_for_tests/*.wasm)
    • check-skipped = build-wasm (wasm-for-tests, build-wasm-tests-scripts, wasm_for_tests/*.wasm)
  • any of [🛡 GitHub branch protection]:
    • check-success = lints
    • check-neutral = lints
    • check-skipped = lints
  • any of [🛡 GitHub branch protection]:
    • check-success = rust-docs
    • check-neutral = rust-docs
    • check-skipped = rust-docs
  • any of [🛡 GitHub branch protection]:
    • check-success = test-wasm
    • check-neutral = test-wasm
    • check-skipped = test-wasm
  • any of [🛡 GitHub branch protection]:
    • check-success = test-e2e (0)
    • check-neutral = test-e2e (0)
    • check-skipped = test-e2e (0)
  • any of [🛡 GitHub branch protection]:
    • check-success = test-e2e (1)
    • check-neutral = test-e2e (1)
    • check-skipped = test-e2e (1)
  • any of [🛡 GitHub branch protection]:
    • check-success = test-e2e (2)
    • check-neutral = test-e2e (2)
    • check-skipped = test-e2e (2)
  • any of [🛡 GitHub branch protection]:
    • check-success = test-e2e (3)
    • check-neutral = test-e2e (3)
    • check-skipped = test-e2e (3)
  • any of [🛡 GitHub branch protection]:
    • check-success = test-e2e (4)
    • check-neutral = test-e2e (4)
    • check-skipped = test-e2e (4)
  • any of [🛡 GitHub branch protection]:
    • check-success = test-integration
    • check-neutral = test-integration
    • check-skipped = test-integration
  • any of [🛡 GitHub branch protection]:
    • check-success = test-unit
    • check-neutral = test-unit
    • check-skipped = test-unit
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections

@mergify mergify Bot added the queued label Aug 6, 2026
@mergify
mergify Bot merged commit e6f207c into main Aug 6, 2026
25 of 26 checks passed
@mergify
mergify Bot deleted the use-gh-runners-ci branch August 6, 2026 10:30
@mergify mergify Bot removed the queued label Aug 6, 2026
@Fraccaman Fraccaman added the backport-201.0 Backport to app 201.0 maintenance branch label Aug 6, 2026
@mergify mergify Bot mentioned this pull request Aug 6, 2026
3 tasks
mergify Bot added a commit that referenced this pull request Aug 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-201.0 Backport to app 201.0 maintenance branch breaking:api public API breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants