ci: enforce the committed lockfile - #614
Merged
Merged
Conversation
Co-authored-by: OpenAI Codex <codex@openai.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
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.
Summary
--lockedto Clippy--lockedthrough both Cargo and cross build/test pathsDust is a binary application with a committed
Cargo.lock. Without--locked, Cargo can repair manifest/lockfile drift only inside a runner, leaving normal CI green while a stricter downstream or release invocation fails.Validation
cargo check --locked --all-targetsgit diff --checkPrepared with assistance from OpenAI Codex; the commit includes a
Co-authored-bytrailer.