chore(deps): regenerate the lockfile for the minor-and-patch group (supersedes #638) - #651
Merged
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Applies the seven dependency bumps from #638 on top of current main and regenerates pnpm-lock.yaml natively, which is the workaround #540 documents. The bot's own lockfile could not be used as-is: it dropped the `overrides:` header AND re-resolved satori to the vulnerable fflate 0.7.3 (GHSA-px8p-9vwx-vf98). Per #540's standing instruction -- "Do not repair only the header: regenerate and inspect the resolved graph" -- the resolved graph was inspected rather than assumed. fflate@0.7.3 is absent from the tree entirely; satori@0.33.4 resolves fflate 0.7.5. scripts/ci/check-lockfile-overrides.py (added in #639) passes, and it is the check that rejects the bot's version of this same lockfile. @astrojs/markdown-remark ^7.3.0 -> ^7.3.1 astro ^7.3.1 -> ^7.3.3 markdown-it ^15.0.1 -> ^15.0.2 svelte ^5.57.0 -> ^5.57.1 @typescript-eslint/parser ^8.69.0 -> ^8.70.0 eslint ^10.10.0 -> ^10.11.0 eslint-plugin-astro ^3.1.0 -> ^3.2.1 frozen install clean, build 0, astro check 0 errors, eslint 0 errors, 5/5 design audits, 48/48 unit. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015AvTumDxQ2ntLDwsSefHtf
williamzujkowski
force-pushed
the
pr638-fix
branch
from
September 24, 2026 04:27
fbad5f7 to
9fade97
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.
Applies the seven dependency bumps from #638 on top of current main, with the lockfile regenerated natively — the workaround #540 documents.
The bot's own lockfile could not be used as-is. It dropped the
overrides:header and re-resolved satori back to the vulnerablefflate@0.7.3(GHSA-px8p-9vwx-vf98).Per #540's standing instruction — "Do not repair only the header: regenerate and inspect the resolved graph" — the graph was inspected rather than assumed:
fflate@0.7.3is absent from the tree entirely.scripts/ci/check-lockfile-overrides.py(added in #639) passes here — and it is the check that rejects the bot's version of this same lockfile.@astrojs/markdown-remarkastromarkdown-itsvelte@typescript-eslint/parsereslinteslint-plugin-astroCloses #638 once merged.
Verification
frozen install clean · build 0 ·
astro check0 errors · eslint 0 errors · 5/5 design audits · 48/48 unit🤖 Generated with Claude Code
https://claude.ai/code/session_015AvTumDxQ2ntLDwsSefHtf