fix: regenerate dependencies-cargo.json to match Cargo.lock#160
Merged
Conversation
The base64 0.22.1 crate was promoted from a transitive to a direct Cargo dependency without regenerating the supply-chain data, so a clean run of website/scripts/generate-deps.js modified the committed JSON and the nightly security audit failed its supply-chain FAIL IF check. Regenerate the file: base64 moves to the direct section with a declaredName field. Re-running the generator now produces no diff. Fixes #159 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Deploying mouseterm with
|
| Latest commit: |
86a3c75
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2cd1d285.mouseterm.pages.dev |
| Branch Preview URL: | https://fix-regenerate-cargo-supply.mouseterm.pages.dev |
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.
Regenerate
dependencies-cargo.jsonto matchCargo.lockFixes #159 — the nightly security audit failed its supply-chain
FAIL IFcheck: runningnode website/scripts/generate-deps.jsfrom a clean checkout modifiedwebsite/src/data/dependencies-cargo.json, meaning the committed supply-chain data had drifted from the actual Cargo dependency graph.The
base64 0.22.1crate had been promoted from a transitive to a direct dependency (it now carries adeclaredName), but the generated supply-chain JSON was never regenerated and committed. SECURITY.md requires the generated supply-chain files to stay in sync with every dependency change, so the disclosed dependency list on the website's supply-chain page no longer matchedCargo.lock.This PR runs the generator and commits its output:
base64moves from thetransitivesection todirect(gainingdeclaredName), an 8-insertion / 7-deletion change — exactly the drift the audit reported.Verification
node website/scripts/generate-deps.jsagainstmain(7f88741) produced the same8 insertions, 7 deletionsdiff todependencies-cargo.json.dependencies-cargo.jsonchanged; the npm and runtime supply-chain files were already in sync.No separate regression test is added: the security-audit workflow's
FAIL IFcheck (generator must not modify committed files) is itself the regression gate, and it now passes.