Repository navigation
ci: track the pinned 1.95.0 toolchain in ci and publish - #21
Merged
Merged
Conversation
rust-toolchain.toml landed at 1.95.0 (PR #20); the workflows still installed and invoked 1.88.0 explicitly. All rustup installs and cargo invocations now use 1.95.0. The declared rust-version 1.88 floor for consumers is unchanged.
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.
What
PR #20 pinned
rust-toolchain.tomlto 1.95.0, but both workflows still installed and invoked 1.88.0 explicitly (20 call sites acrossci.ymlandpublish.yml). All now use 1.95.0, matching the pin.The declared
rust-version = 1.88consumer floor is unchanged; this only aligns the CI/publish toolchain with the repo pin.Verification
cargo +1.95.0 check --lockedgreen on this tree (the workflows' fmt/clippy/test steps run the same commands the local run exercised)