deps: bump dtolnay/rust-toolchain to current stable - #166
Merged
Merged
Conversation
- dtolnay rewrites the stable branch, so the pinned commit is no longer reachable from it and zizmor's impostor-commit audit fails every workflow run that references it.
Contributor
soothfast gate |
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
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.
What changed
Every
dtolnay/rust-toolchainpin moves from the August 5stablecommit to the current one,6bed0761d98439e5a578e2877258200ad565ba87(September 3). Seventeenuses:lines across the workflows, nothing else.Why
dtolnay rewrites the
stablebranch rather than appending to it, so the commit the workflows pinned is no longer reachable from any branch or tag in that repository. zizmor's onlineimpostor-commitaudit treats such a pin as an error, and the code-scanning check it feeds went red on #165 for that reason alone. The same alert will fire on master and on every stacked PR at its next Security run, so this lands first and the stack rebases onto it.How was this tested
6bed0761d98439e5a578e2877258200ad565ba87is the head ofdtolnay/rust-toolchain@stablevia the GitHub API.Checklist
make checkpasses (fmt, clippy-D warnings,cargo test --workspace)make gate BASE=masterpasses, or any intentional cost change is explained above///doc commentsREADME.md,docs/,soothfast:bind/soothfast:claimmarkers) updated if behavior changed