chore(deps): update third-party crates - #991
Merged
Merged
Conversation
Bump nickel-lang-core's pinned git rev from e8a0ab95 (2026-06-17) to 0d306feb (2026-07-26), 32 commits upstream. Picks up a std.string.find panic fix on a match at the end of the string, a parse fix for negative number literals in match patterns, and new std.array.chunk/group plus a merge-sort std.array.sort. Stays on the git rev deliberately: crates.io's newest release (0.18.0) lags master by a long way, so the old "revert to crates.io once released" note is replaced with the actual rationale. hakoniwa is already at the latest upstream release (1.7.2); no change. Also: - serial_test 3 -> 4 (dev-dep; needs Rust 1.93.1, under our 1.97.0 pin). - clap/clap_complete 4.5 -> 4.6 in the manifest. The lockfile already resolved 4.6.4/4.6.8 since ^4.5 admits 4.6, so this changes no resolution; it drops a stale comment whose stated cause (c2rust-bitfields' exact proc-macro2 pin via tun-rs) is no longer in the tree at all. - cargo update within semver: aes, cc, jiff, rustls-pki-types, schemars, toml_parser. - rand_core stays at 0.6 (documented, matches boringtun/x25519-dalek). Document why the google-cloud-* / reqwest cluster resolves below its latest releases: reqwest >= 0.13.2 pulls js-sys >= 0.3.85, which requires an exact wasm-bindgen =0.2.108, while nickel's `format` feature reaches topiary-tree-sitter-facade, which pins =0.2.100. The two cannot unify, so the resolver silently freezes the cluster. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
📝 WalkthroughWalkthrough
ChangesWorkspace dependency updates
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
Comment |
norrietaylor
approved these changes
Jul 28, 2026
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
2 participants
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.
Bump nickel-lang-core's pinned git rev from e8a0ab95 (2026-06-17) to 0d306feb (2026-07-26), 32 commits upstream. Picks up a std.string.find panic fix on a match at the end of the string, a parse fix for negative number literals in match patterns, and new std.array.chunk/group plus a merge-sort std.array.sort. Stays on the git rev deliberately: crates.io's newest release (0.18.0) lags master by a long way, so the old "revert to crates.io once released" note is replaced with the actual rationale.
hakoniwa is already at the latest upstream release (1.7.2); no change.
Also:
Documents why the google-cloud-* / reqwest cluster resolves below its latest releases: reqwest >= 0.13.2 pulls js-sys >= 0.3.85, which requires an exact wasm-bindgen =0.2.108, while nickel's
formatfeature reaches topiary-tree-sitter-facade, which pins =0.2.100. The two cannot unify, so the resolver silently freezes the cluster.Note
Update third-party crates including clap, serial_test, and nickel-lang-core
clapandclap_completefrom 4.5 to 4.6, andserial_testfrom 3 to 4nickel-lang-coregit revision to0d306febwith expanded comments explaining the pin rationalegoogle-cloud-*/reqwestandwasm-bindgenpinningMacroscope summarized afd5e17.
Summary by CodeRabbit