chore(deps): bump transitive fast-uri to 3.1.4 (Dependabot alerts #20, #21) - #148
Merged
Conversation
…20+21 fast-uri 3.1.2 (sole instance, via ajv@8.20.0 in the storybook/webpack devDependency chain) is vulnerable to GHSA-4c8g-83qw-93j6 and GHSA-v2hh-gcrm-f6hx (host-confusion, both high). 3.1.4 is the first version patched for both. Lockfile-only: ajv's ^3.0.1 range already admits 3.1.4, and `pnpm update fast-uri` (incl. --depth Infinity) won't re-resolve a transitive dep, so the three lockfile entries are edited directly with the registry integrity hash and validated via `pnpm install --frozen-lockfile` ("Lockfile passes supply-chain policies"). Not 3.1.5: published today, so pnpm's minimumReleaseAge quarantine rejects it (ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION); a future lock-file-maintenance run will float to it once it ages out. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Aug 1, 2026
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
2 participants
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.
Fixes the two open high-severity Dependabot alerts:
What changed:
pnpm-lock.yamlonly — the singlefast-uri@3.1.2instance floats to 3.1.4 withinajv@8.20.0's existing^3.0.1range. fast-uri lives entirely in the storybook/webpack devDependency chain (ajv → ajv-formats/schema-utils → webpack → @storybook/nextjs), so there's no production runtime exposure; this clears the alerts and the build toolchain.Why hand-edited:
pnpm update fast-uri(with and without--depth Infinity) won't re-resolve a transitive-only dep, so the three lockfile entries were edited directly with the registry integrity hash, then validated:pnpm install --frozen-lockfilepasses ("✓ Lockfile passes supply-chain policies, 920 entries") andnode_modules/.pnpm/ajv@8.20.0/node_modules/fast-urilinks 3.1.4.Why not 3.1.5: it was published today (2026-07-31T09:16Z) and pnpm's
minimumReleaseAgequarantine correctly rejects it (ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION). 3.1.4 (published 2026-07-19) is the first version patched for both advisories; the next lock-file-maintenance run will float to 3.1.5+ once it ages out.Local verification (macOS, Node 26, pnpm 11.17.0): frozen install ✅ ·
pnpm typecheck✅ ·pnpm test445 tests, 441 pass / 4 skip / 0 fail ✅ ·pnpm build✅ ·pnpm build-storybook(the chain that actually consumes fast-uri) ✅Out of scope, deliberately: #132 (TypeScript v7) stays untouched — Next doesn't support it yet.
🤖 Generated with Claude Code