fix(deps): take nanoid 3.3.18 past GHSA-2v37-7h3g-55p8 - #28
Merged
Conversation
A newly published high-severity advisory covers nanoid < 3.3.18, which is a different one from the y-indexeddb advisory pinned in #26 and arrives by a different path — postcss, not Keystatic. No override this time. postcss already asks for ^3.3.16, so the patch was always in range and only the lockfile was holding 3.3.17. The three-line lockfile bump is the whole fix, and adding an override here would have left a permanent pin behind for a problem npm can resolve on its own. npm audit reports 0 vulnerabilities; the audit-level=high CI gate exits 0 again. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LaydoxAZ4eaqqPNKrmWLbt
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
npm auditwent red again onmain. This is not the advisory #26 pinned.@toeverything/y-indexeddbThe reasoning recorded in #26 — that a global
nanoidoverride was wrong because postcss'snanoid@3.3.17sat outside the affected range — is now obsolete. 3.3.17 is inside this one.No override was added. postcss already depends on
^3.3.16, so 3.3.18 was always in range and only the lockfile was pinning 3.3.17.npm update nanoidis the entire fix: three lines, one package. An override here would have left a permanent pin behind for something npm resolves on its own.Verification
npm audit→ 0 vulnerabilities;npm audit --audit-level=highexits 0This unblocks #27, whose CI fails on the same gate for the same reason.
🤖 Generated with Claude Code
https://claude.ai/code/session_01LaydoxAZ4eaqqPNKrmWLbt