[dependabot]

Bumps the all-security group with 1 update in the / directory: fast-uri.

Updates fast-uri from 3.1.5 to 3.1.9

Release notes

Sourced from fast-uri's releases.

v3.1.9

Security

This security release fixes four URI parsing and normalization vulnerabilities in fast-uri 3.x. Applications that process untrusted URI input should upgrade to v3.1.9.

• Medium — URI scheme spoofing through percent-encoded schemes (GHSA-w74x-v6f9-j3xg, CVE-2026-110306): percent-encoded scheme input is now rejected instead of being decoded into a live scheme.
• Medium — Host confusion during domain-host canonicalization (GHSA-wjr9-j795-jxcr, CVE-2026-110180): malformed domain hosts containing ambiguous delimiters or stripped control characters are now rejected instead of being silently rewritten.
• Low — Incorrect relative-reference normalization (GHSA-xhq7-xmqj-769h, CVE-2026-110095): dot-segment removal now preserves the resolution semantics of relative references.
• Low — Scheme injection in suffix references (GHSA-333x-w4r6-6crp, CVE-2026-110725): first-segment colons in path-only suffix references are now escaped so the output is not reparsed as a scheme.

Upgrade with:

npm install fast-uri@3.1.9

Thanks to @​zekth for reporting the scheme, host, and relative-reference issues, and to @​UlisesGascon for finding the suffix-reference issue and reviewing the remediations.

What's Changed

• ci: enable trusted publishing releases (v3.x) by @​mcollina in fastify/fast-uri#229

Full Changelog: fastify/fast-uri@v3.1.8...v3.1.9

v3.1.8

⚠️ Security Warning

This security release fixes the following medium-severity security advisory:

• GHSA-hrr3-gc8f-f4qj — inconsistent host case normalization via percent-encoded octets

Users of the v3.x release line should upgrade to v3.1.8.

Full Changelog: fastify/fast-uri@v3.1.7...v3.1.8

v3.1.7

⚠️ Security Warning

This is a security release that fixes the following high-severity security advisories:

• GHSA-qw65-cvwx-89v3 — authority injection via an unvalidated port in serialize()
• GHSA-58mr-gqgx-xq4g — host confusion via unbalanced or misplaced IP-literal brackets

Users of the v3.x release line should upgrade to v3.1.7.

Full Changelog: fastify/fast-uri@v3.1.6...v3.1.7

v3.1.6

⚠️ Security Warning

... (truncated)

Commits

• 0def703 Bumped v3.1.9
• a1d0da2 test: generate only relative path references
• 9eb8759 fix: preserve relative paths in suffix and relative resolution
• 54c30f7 docs: note suffix-reference authority ambiguity
• 39e6493 fix: escape a first-segment colon in suffix references
• 745183c test: cover first-segment colon in suffix references
• ddfc6a5 fix(SEC-03): reject non reg-name characters in domain hosts
• d86a8d2 fix: keep a colon-first segment behind "./" in relative normalization
• eb483b5 test: cover colon-first relative references in normalization
• b110a35 fix(SEC-02): preserve meaning of relative references during normalization
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for fast-uri since your current version.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[github-actions]

Visual parity — dark theme 🌙

Every captured route is pixel-identical to the merge base across 1440x1000 (40 routes) and 420x900 (40 routes).

Enforced: this PR is labelled dependencies, so a dependency bump that moves rendering fails here rather than merging silently.

[github-actions]

Visual parity — light theme ☀️

Every captured route is pixel-identical to the merge base across 1440x1000 (40 routes) and 420x900 (40 routes).

Enforced: this PR is labelled dependencies, so a dependency bump that moves rendering fails here rather than merging silently.

[axsaucedo]

Dependabot fix report

PR context

PR 143 is a low-risk npm all-security update of transitive dev dependency fast-uri from 3.1.5 to 3.1.9. It changes only the package-lock entry (3 additions, 3 deletions); package.json, source, public assets, and build configuration are unchanged. The release addresses multiple URI parsing and normalization vulnerabilities.

Symptoms and root cause

The required lint, typecheck, and build checks passed. The only failure was dark visual parity on /talks-and-events/ at 1440px: 49,400 pixels with a peak channel delta of 236. Mobile dark parity and both light viewports passed.

fast-uri is used only through @astrojs/check -> @astrojs/language-server -> volar-service-yaml -> yaml-language-server -> ajv; it is not imported by first-party code and does not reach the production build. The isolated visual result was a capture flake involving remote raster media on the talks page. Repeated runs of this identical lockfile-only update have alternated between fully green and that one mismatch, while merge-base and head HTML fingerprints are byte-identical.

No repository edit was appropriate. I reran the known-flaky failed job once after clean local validation.

Testing evidence

• Node 22.22.3 and npm 11.19.1 from the asdf shims
• npm ci: passed
• npm run lint: passed
• npm run format:check: passed
• npm run check:ratchet: passed with 0 errors, warnings, or hints; style and motion ratchets passed
• npm run build: passed, including Pagefind completion
• Worktree: clean; no fix commit or push was needed
• Current CI: lint, typecheck, build, motion, visual (dark), and visual (light) all pass

Phase E parity decision and result

Parity was run because Step 8.5's complete skip criteria were not met: this is an npm lockfile change, not a GitHub-Actions-only or .github/**-only change. A local Chromium launch was blocked by the managed macOS sandbox, so that local capture was treated as void. The repository's canonical GitHub merge-base parity workflow was rerun on the same head instead, rebuilding and capturing both revisions with strict zero tolerance and no allowlist.

• Dark: pixel-identical, 40 routes at 1440x1000 and 40 routes at 420x900
• Light: pixel-identical, 40 routes at 1440x1000 and 40 routes at 420x900
• Total: 160 clean comparisons, 0 differing pixels, no missing routes, no size mismatches

The dark rerun evidence is recorded in tmp/parity/1440.json and tmp/parity/420.json in the autonomous fresh clone; the report and scratch evidence remain gitignored and were not committed.

Recommendation

Ready to merge. The PR is mergeable, all checks are green, and strict merge-base parity is clean. It remains open because the orchestrator, not this run, owns the merge decision.