fix: update nanoid security patches - #17
Merged
Merged
Conversation
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.
Summary
nanoidfrom 5.1.11 to 5.1.16nanoid3.3.18Why
The direct dependency is affected by CVE-2026-67214, and the prior transitive 3.x release has a separate high-severity advisory. Both paths now use patched releases with no application-code changes.
Validation
pnpm lint:checkpnpm test(5 tests passed)pnpm buildpnpm build:checkpnpm audit --audit-level high(no known vulnerabilities)Merge order
The fixes are independent and may be merged in either order: