chore(security): weekly cargo-vet import refresh - #58
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Scheduled weekly refresh of supply-chain/imports.lock from upstream audit sources (Mozilla, Google, Bytecode Alliance, ISRG, Zcash). See .github/workflows/cargo-vet-refresh.yml for rationale and docs/policies/dependency_policy.md for the full supply-chain posture.
github-actions
Bot
force-pushed
the
chore/cargo-vet-refresh
branch
from
September 14, 2026 14:41
abbae39 to
dc1a26d
Compare
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
Weekly refresh of
supply-chain/imports.lockfrom upstreamaudit sources (Mozilla, Google, Bytecode Alliance, ISRG,
Zcash). Opened automatically by
.github/workflows/cargo-vet-refresh.yml.GitHub suppresses CI runs on PRs opened by the
default
GITHUB_TOKEN(anti-recursion safety). Totrigger the Tier 1 checks:
git fetch origin chore/cargo-vet-refresh git checkout chore/cargo-vet-refresh git commit --allow-empty -S -m "chore: trigger ci" git pushWhat changed
Diff is entirely within
supply-chain/- either addedaudit records or pruned exemptions that are now covered
by upstream audits.
Why review is still needed
Even though the content comes from trusted upstreams,
the merge commit itself must be signed + reviewed per
branch protection. Skim the diff for anything
unusual (e.g. a removed audit record that's been
replaced by an exemption - would indicate an upstream
has retracted an audit, which warrants investigation).