chore(ci): pin dtolnay/rust-toolchain to SHA#237
Merged
Conversation
Replaces all 5 `@stable` refs across build.yml, release.yml, and rust-tests.yml with a SHA pin to 29eef336d9b2848a0b548edc03f92a220660cdb8 (`@stable` head as of 2026-03-27). ## Why `@stable` is a floating ref — any regression dtolnay ships breaks every PR in flight at once, and we have no signal until a build fails. Pinning to SHA freezes our action surface so toolchain changes become explicit lockfile-style updates we choose to take. ## What this does NOT fix The recent macOS `cargo metadata` -> `rustup-init` flake hitting several open PRs (#226, #228, #231, #232, #234) is runner-side, not action-side: this SHA was already what `@stable` resolved to before and during the flake window. Reruns of failed jobs are passing on the same SHA, confirming it's transient runner state, not the action. So this PR is hygiene, not the fix for the current symptom. If the flake persists we'll need to either work around in the workflow (retry on the rust-toolchain step) or switch to `actions-rust-lang/setup-rust-toolchain`. ## Updating later When we want a newer toolchain or action behavior, bump the SHA and update the trailing comment. Dependabot can be configured to track github-actions and propose the bumps. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces all 5
@stablerefs acrossbuild.yml,release.yml, andrust-tests.ymlwith a SHA pin to29eef336d9b2848a0b548edc03f92a220660cdb8(@stablehead as of 2026-03-27).Why
@stableis a floating ref — any regression dtolnay ships breaks every PR in flight at once, and we have no signal until a build fails. Pinning to SHA freezes our action surface so toolchain changes become explicit lockfile-style updates we choose to take.What this does NOT fix
The recent macOS
cargo metadata→rustup-initflake hitting several open PRs (#226, #228, #231, #232, #234) is runner-side, not action-side: this SHA was already what@stableresolved to before and during the flake window. Reruns of failed jobs are passing on the same SHA, confirming it's transient runner state, not the action.So this PR is hygiene, not the fix for the current symptom. If the flake persists we'll need to either:
actions-rust-lang/setup-rust-toolchainUpdating later
When we want a newer toolchain or action behavior, bump the SHA and update the trailing comment. Worth pointing Dependabot at
github-actionsto get auto-proposed bumps for these.🤖 Generated with Claude Code