chore(deps): bump nanoid 3.3.16 -> 3.3.18 - #158
Merged
Conversation
Transitive dep of vite -> postcss. The advisory (high, nanoid <3.3.17) published after #155 landed, so the Security Scanning npm-audit step now fails every master push; it never surfaced on PRs because that job only runs on master. Co-Authored-By: Claude Fable 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.
What
Bump the transitive
nanoidpin inweb/package-lock.jsonfrom 3.3.16 to 3.3.18 (pulled in viavite -> postcss). Lockfile-only; no direct dependency changes.Why
A high-severity advisory for
nanoid <3.3.17(GHSA-2v37-7h3g-55p8 — custom generators can loop indefinitely when size is zero) published after #155 landed. The Security Scanning job'snpm audit --omit=dev --audit-level=highstep now fails every master push (first tripped by #156's merge run); it never shows on PR runs because that job only executes on master.Verification
npm audit --omit=dev --audit-level=high— 0 vulnerabilities (the exact CI command)npm run build— clean🤖 Generated with Claude Code