Repository navigation
chore: refresh Cargo.lock - #34
Merged
Merged
Conversation
codeandsolder-git-wrangler
Bot
deleted the
automation/lockfile-2026-09-18
branch
September 29, 2026 04:13
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.
Refresh the complete lockfile at the repository's intentional Rust 1.94.1 compatibility floor. The passive queue reported cfg-if, jsonwebtoken, rustix, syn, unicode-ident, and ureq-proto updates; the canonical
cargo updatealso accepts any additional compatible/transitive releases available at execution time.The bootstrap workflow generates the Cargo-authored lockfile on GitHub Actions and removes itself in the same commit, leaving only the real maintenance diff for normal repository CI.
Closes #33