Skip to content

chore(deps): patch the fast-uri advisories - #29

Merged
safenestdev merged 1 commit into
mainfrom
fix/fast-uri-advisory
Oct 27, 2026
Merged

safenestdev merged 1 commit into
mainfrom
fix/fast-uri-advisory

Conversation

@safenestdev

Copy link
Copy Markdown
Contributor

The build's npm audit --omit=dev step fails on every branch since four moderate fast-uri advisories were published (GHSA-w74x-v6f9-j3xg, GHSA-xhq7-xmqj-769h, GHSA-wjr9-j795-jxcr, GHSA-333x-w4r6-6crp). This moves fast-uri from 3.1.8 to 3.1.9. Only that lockfile entry changes. Checked: npm ci --dry-run is consistent and npm audit --omit=dev reports 0 vulnerabilities.

fast-uri 3.1.8 to 3.1.9 (GHSA-w74x-v6f9-j3xg, GHSA-xhq7-xmqj-769h,
GHSA-wjr9-j795-jxcr, GHSA-333x-w4r6-6crp, moderate). The npm audit step failed
every build. Lockfile entry only.

@lena-sabadina lena-sabadina left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, thanks for the quick fix.

  • The sha512 integrity hash and tarball URL for fast-uri 3.1.9 match what the npm registry publishes.
  • The diff is limited to the fast-uri lockfile entry, with no unrelated churn, and a patch bump within 3.1.x is low risk.
  • build, CodeQL and Analyze all pass, including the npm audit --omit=dev step.

One optional thought, not a blocker: fast-uri is a transitive dependency, so a future lockfile regeneration could resolve a different version. An overrides entry would pin it if you ever want that guarantee, but the lockfile bump is the right size for this fix.

@safenestdev
safenestdev merged commit ef64800 into main Oct 27, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants