chore(website): regenerate dependency supply-chain snapshots#193
Merged
Conversation
Deploying mouseterm with
|
| Latest commit: |
0a85f9f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://2213f682.mouseterm.pages.dev |
| Branch Preview URL: | https://chore-regenerate-dep-snapsho.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.
Regenerates the public supply-chain snapshot pages (
website/src/data/dependencies-npm.jsonanddependencies-cargo.json) so they match the current lockfiles.The nightly
security-audithas flagged check #1 (node website/scripts/generate-deps.jsmust not modify the committed snapshots) as FAIL for four consecutive days (2026-06-26 through 06-30, #191). Several npm and Cargo dependencies were bumped in the lockfiles without the snapshots being regenerated, sodormouse.sh/supply-chaindid not reflect the versions users actually receive.Running the generator picks up the drift, including:
@stricli/core1.2.7→1.2.8,@tauri-apps/api2.11.0→2.11.1, the@xterm/*beta line 0.219→0.288, and the newly-addedcross-spawn7.0.6 (from thedorWindows-spawn work).serde_json1.0.149→1.0.150,tauri2.11.2→2.11.3, and other transitive bumps.dependencies-runtime.jsonis unchanged.No regression test: this is a generated-data refresh, not a code change. The recurring drift is what
security-auditcheck #1 already guards — this PR just brings the committed output back in sync.Fixes #191.