Repository navigation
chore(deps): bump nanoid to 3.3.18 (Dependabot #70, high) - #14
Merged
Merged
Conversation
Resolves Dependabot alert #70 (GHSA-2v37-7h3g-55p8, high). nanoid is transitive via postcss <- vitest; pnpm update -r resolves it within postcss's existing ^3.3.x range, so no overrides entry is needed. Verified: pnpm install --frozen-lockfile, pnpm run verify (boundaries OK, typecheck clean, 170 tests passed / 3 skipped) on Node 22 + pnpm 10.28.2 (matches .github/workflows/ci.yml).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch had an error being deployed
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.
What
Bumps
nanoid3.3.16→3.3.18in the rootpnpm-lock.yaml.Why
Dependabot alert #70 — GHSA-2v37-7h3g-55p8 (high), vulnerable range
< 3.3.18. This is the only alert on the live RuneBolt tree; the other 63 are in the frozenlegacy/taproot-assets-eraprototype and are handled separately.nanoidis a transitive dependency (postcss←vitest, devDependency scope).pnpm update nanoid -rresolves it insidepostcss's existing^3.3.xrange, so nopnpm.overridesentry is required — the diff is 4 lines and touches nothing else.How verified
Node 22 + pnpm 10.28.2, matching
.github/workflows/ci.yml:pnpm install --frozen-lockfile— cleanpnpm run verify:lint:boundaries— boundary check OK (10 files, 1 rule)typecheck— cleantest— 170 passed, 3 skipped (live-network tests), 12 filesLockfile diff is confined to the three
nanoidreferences.