Repository navigation
ci: re-pin the release build toolchain action to a reachable commit - #92
Merged
Merged
Conversation
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.
The release build job pinned dtolnay/rust-toolchain to 4cda84d5, a commit on the action's
stablebranch. That branch is rebased onto every master commit, and the compare API now reports 4cda84d5 as diverged from master, so no branch reaches it. If GitHub garbage-collects it, the next tagged release fails at toolchain setup.This re-pins it to e2a55d2f (master, 2026-10-09), the same pin ci.yml uses since #91, and adds
toolchain: stable, which the master action requires.