chore(ci): switch back to github-hosted runners#10144
Conversation
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
Greptile SummaryThis PR migrates all CI jobs from Namespace self-hosted runners to GitHub-hosted
Confidence Score: 5/5Safe to merge — changes are purely infrastructure (runner labels, cache provider) and registry test-expectation corrections with no runtime logic altered. The runner swap and cache action replacement follow a consistent, well-tested pattern already used elsewhere in the repo. The save-if gating, lint-job ordering fix, and trigger expansions are all correct. Registry corrections align expected output with what the tools actually emit. The only gap is the removed amp test entry, which reduces automated coverage for that tool but does not break anything. registry/amp.toml — the test field was dropped; worth confirming whether @ampcode/cli exposes a --version flag that could restore automated verification. Important Files Changed
Reviews (10): Last reviewed commit: "chore(ci): switch back to github-hosted ..." | Re-trigger Greptile |
71eac1a to
6a252ce
Compare
| if: github.repository == 'jdx/mise' | ||
| timeout-minutes: 20 | ||
| runs-on: namespace-profile-endev-linux-amd64;overrides.cache-tag=mise-release-plz-rust-linux | ||
| runs-on: ubuntu-latest |
There was a problem hiding this comment.
Missing rust-cache step in release-plz workflow
Medium Severity
The release-plz.yml workflow switched from a Namespace runner (which had implicit filesystem-level caching via the cache-tag override) to ubuntu-latest, but unlike every other workflow that performs a cargo build, no Swatinem/rust-cache step was added. The workflow runs cargo build --all-features on every push to main and on a daily cron, and the 20-minute timeout may not be sufficient for uncached builds on a standard GitHub-hosted runner.
Reviewed by Cursor Bugbot for commit 6a252ce. Configure here.
There was a problem hiding this comment.
Leaving this unchanged intentionally: we do not want to use cache on release workflows/builds, so release-plz should stay uncached even though it now runs on ubuntu-latest.
This comment was generated by an AI coding assistant.
Hyperfine Performance
|
| Command | Mean [ms] | Min [ms] | Max [ms] | Relative |
|---|---|---|---|---|
mise-2026.5.16 x -- echo |
22.9 ± 0.5 | 22.0 | 28.3 | 1.00 ± 0.03 |
mise x -- echo |
22.8 ± 0.4 | 22.1 | 25.6 | 1.00 |
mise env
| Command | Mean [ms] | Min [ms] | Max [ms] | Relative |
|---|---|---|---|---|
mise-2026.5.16 env |
22.4 ± 0.7 | 21.7 | 28.6 | 1.01 ± 0.03 |
mise env |
22.2 ± 0.4 | 21.3 | 24.6 | 1.00 |
mise hook-env
| Command | Mean [ms] | Min [ms] | Max [ms] | Relative |
|---|---|---|---|---|
mise-2026.5.16 hook-env |
23.1 ± 0.4 | 22.3 | 25.1 | 1.00 ± 0.02 |
mise hook-env |
23.0 ± 0.4 | 22.2 | 24.8 | 1.00 |
mise ls
| Command | Mean [ms] | Min [ms] | Max [ms] | Relative |
|---|---|---|---|---|
mise-2026.5.16 ls |
20.2 ± 0.3 | 19.5 | 22.1 | 1.01 ± 0.03 |
mise ls |
20.1 ± 0.4 | 19.3 | 23.6 | 1.00 |
xtasks/test/perf
| Command | mise-2026.5.16 | mise | Variance |
|---|---|---|---|
| install (cached) | 171ms | 167ms | +2% |
| ls (cached) | 84ms | 82ms | +2% |
| bin-paths (cached) | 89ms | 86ms | +3% |
| task-ls (cached) | 154ms | 150ms | +2% |
6a252ce to
d5b54e5
Compare
d5b54e5 to
a7851e5
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
There are 2 total unresolved issues (including 1 from previous review).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit a7851e5. Configure here.
8e9daf7 to
b0382b4
Compare
b0382b4 to
9e4c960
Compare


Summary
ubuntu-latest/macos-latestnamespacelabs/nscloud-cache-actionsteps with the repo's existing pinnedSwatinem/rust-cachepattern outsiderelease.yml.github/workflows/release.ymlcache-free; its jobs only switch runner labelsmainandreleasebranch refs while keeping PR refs read-onlytest-vfoxonmainandreleaseso its Rust cache can be savedtestworkflow on release-branch pushes and setTEST_ALL=1therewash,ghcup,infisical, andampexposed by the full registry matrixTest
mise run buildMISE_EXPERIMENTAL=1 MISE_LOCKFILE=1 MISE_USE_VERSIONS_HOST_TRACK=0 RUST_BACKTRACE=1 target/debug/mise test-tool --jobs=1 wash ghcup infisicalnpm_config_yes=true npx @sourcegraph/[email protected] --helprg -n "namespace-profile|namespacelabs/nscloud-cache-action" .github/workflows .github/actions || truerg -n "cache|Swatinem/rust-cache|actions/cache|nscloud-cache|sccache|RUSTC_WRAPPER|SCCACHE" .github/workflows/release.yml || truegit diff --checkactionlint -ignore 'SC2129'Note: plain
actionlintstill reports the existingSC2129style warning inregistry.yml; ignored here to validate this runner/cache change.Note
Medium Risk
Broad CI runner and caching changes can slow builds or break PR workflows; registry backend/test edits affect tool installs in production registry paths.
Overview
Moves CI off Namespace self-hosted runners to GitHub-hosted
ubuntu-latest/macos-latestacross docs, test, registry, hyperfine, release-plz, and related workflows.release.ymlonly changes runner labels; it stays without the new Rust cache steps.Replaces
namespacelabs/nscloud-cache-actionwith pinnedSwatinem/rust-cache(still paired with sccache where used). Cache writes are limited tomainandreleaserefs; PRs stay restore-only.testandtest-vfoxnow run onreleasepushes so caches can be saved;teste2e setsTEST_ALL=1on the release branch.Registry fixes for stale
test-toolexpectations:wash/ghcupversion strings,infisicalGitHub asset pattern, andampnpm backend (@ampcode/cliwithallow_builds).Reviewed by Cursor Bugbot for commit 9e4c960. Bugbot is set up for automated code reviews on this repo. Configure here.