Upgrade the docs site to Next 16 and React 19:
- next 15.5.9 -> 16.3.0
- react / react-dom 18.2.0 -> 19.2.8
- @vercel/analytics 1.1.1 -> 2.0.1
- docsgpt-react 0.5.1 -> 0.6.3
- pagefind 1.4.0 -> 1.5.2
- typescript 5.9.3 -> 6.0.3
Two deliberate holds:
Next 16 makes Turbopack the default builder, but nextra 4.6.1 is not
compatible with it. Its loader calls transformerTwoslash() at module top
level, and twoslash gets an undefined ts.sys inside Turbopack's
webpack-loader shim, so every .mdx file fails to compile. Nextra offers no
option to disable twoslash, so the dev and build scripts opt out with
--webpack until nextra supports Turbopack.
typescript stays on 6.0.3 rather than 7.0.2 for the same reason: TS 7 is the
native rewrite and drops the ts.sys API that @typescript/vfs and twoslash
rely on, which breaks the build even under webpack. twoslash declares
typescript ^5.5.0 || ^6.0.0, so 6.0.3 is the ceiling this toolchain supports.
nextra and nextra-theme-docs were already at the latest 4.6.1.
URLCheck read the host from a regex capture group whose character class
excluded "@", so a userinfo-prefixed URL passed its userinfo off as the
host: https://allowed.com@evil.tld/ satisfied an allow_hosts entry for
allowed.com, and http://ok.com@blocked.tld/ evaded block_hosts. Match the
whole URL and take the host from the parsed authority instead. A URL that
will not parse is now redacted rather than waved through.
The PRIVATE_KEY secret pattern matched only the BEGIN header, so a redact
action masked the header and released the key material and END line in
the clear. Span the whole armored block, falling back to the header when
the block is unterminated or over the cap, and raise max_match_chars so
the streaming guard's window still covers a full PEM. The pattern also
now catches ENCRYPTED, DSA and PGP BLOCK headers, which it missed
entirely.
The documented GUARDRAILS_FLOOR example omitted "enabled": true, and the
field defaults to false, so an operator copying it got a floor that
parsed clean, merged to nothing and warned nowhere. Fix the example and
warn when a floor is set but disabled.
Lockfile-only update; package.json is unchanged.
extensions/react-widget is published as the npm package `docsgpt` and as an
HTML embed, so its production dependency tree reaches every consumer. That
tree carried 5 advisories (2 high, 2 moderate, 1 low), 7 across the full tree.
dompurify 3.4.0 -> 3.4.13 (moderate, XSS)
js-yaml 4.1.1 -> 4.3.1 (high, quadratic-complexity DoS)
linkify-it 5.0.0 -> 5.0.2 (high)
markdown-it 14.1.0 -> 14.3.0 (moderate)
svgo 4.0.1 -> 4.0.2 (high, dev)
brace-expansion 1.1.12 -> 1.1.18 (high, CVE-2026-13149; nested copies)
@babel/core 7.29.0 -> 7.29.7 (low)
npm audit goes 7 -> 0 (production tree 5 -> 0). Verified locally: clean
npm ci, `npm run build` (embed) and `npm run build:react` (library) both
build, npm run lint and tsc --noEmit pass.
Alex