chore: ship v0.5.103 (version bump + supply-chain vet)#318
Merged
Conversation
The ship's `cargo update` advanced six transitive deps past their vetted versions, failing `cargo vet`. Real audits recorded (no lazy exemption bumps): - memchr 2.8.1, serde_json 1.0.150: publisher-trust entries — isrg, mozilla, and bytecode-alliance all trust the publishers (BurntSushi, dtolnay respectively). `cargo vet trust`. - crypto-common 0.1.6->0.1.7: metadata-only (generic-array pin, cargo resolver=2); zero .rs changes. - crypto-common 0.1.6->0.2.2: generic-array->hybrid_array API restructure; net zero new unsafe blocks; new generate.rs is safe rand_core-trait RNG-array gen; no FFI/IO/capability. - either 1.15.0->1.16.0: the two unsafe Pin::new_unchecked projections are unchanged (map_either!->map_both! rename); rest is safe iterator/ serde impls. - mimalloc 0.1.50->0.1.51: metadata-only (win_direct_tls passthrough feature); zero .rs changes. - libmimalloc-sys 0.1.47->0.1.48: build.rs adds an OUT_DIR C++17 #include wrapper for the MSVC atomics path (paths from CARGO_MANIFEST_DIR/OUT_DIR, no untrusted input); vendored C is an upstream microsoft/mimalloc point-release sync (v2 2.3.1->2.3.2, v3 3.3.1->3.3.2); reviewed the 3272-line C delta for injected logic — no network/exec/exfil/env-hijack introduced. `cargo vet prune` removed the now-superseded exemptions for crypto-common/memchr/serde_json old versions. `cargo vet` passes. Vet-Reviewed-Diff: crypto-common@0.1.6->0.1.7 Vet-Reviewed-Diff: crypto-common@0.1.6->0.2.2 Vet-Reviewed-Diff: either@1.15.0->1.16.0 Vet-Reviewed-Diff: mimalloc@0.1.50->0.1.51 Vet-Reviewed-Diff: libmimalloc-sys@0.1.47->0.1.48 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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
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.
Summary
The
just ship-freshrelease flow bumped the workspace to v0.5.103 and rancargo update, which advanced six transitive deps past their vetted versions. This PR carries the bump and the real supply-chain vetting needed to satisfycargo vet+ thevet-audit-disciplinegate.Branch protection requires changes via PR (the ship's direct-push-to-main was rejected by the
main-protectionruleset), so the ship commits land here instead.Commits
chore: development v0.5.103 ... [auto-commit]— the ship's version bump + changelog.chore(supply-chain): vet 6 deps bumped by the v0.5.103 ship cargo-update— real audits (no lazy exemption bumps):memchrserde_jsoncrypto-common.rschangescrypto-commonunsafe; safe RNG-array geneitherunsafePin projections unchanged (macro rename); rest safe implsmimallocwin_direct_tlspassthrough), zero.rschangeslibmimalloc-syscargo vet pruneremoved the superseded exemptions. Each delta audit carries aVet-Reviewed-Diff:commit trailer.Validation
Local
lint-pre-pushpassed fully, includingvet✅ andvet-audit-discipline✅, plus clippy (Linux + Windows), tests, rustdoc, deny.🤖 Generated with Claude Code