Repository navigation
Update dependencies - #48
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
npm 11's `npm update` converts v2 lockfiles to v3 regardless, and v2's extra v1 data only serves npm 6, which nothing here uses. No resolved versions change; the v1 `dependencies` section is dropped. Co-Authored-By: Claude Opus 5.5 <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.
Patch and minor updates only; there are no majors and no overrides. The lockfile moves to v3 in its own commit; no resolved versions change.
npm auditstill reports high-severity advisories inundici,basic-ftp, and theproxy-agentchain, all pulled in byrelease-it, which pins them exactly. The only fix npm offers is downgrading torelease-itv20. They're dev-only and never ship to consumers.🤖 Generated with Claude Code