nitropack
2.13.6 · 2 Nov 2026MIT3.9M / weekRepositoryHomepagenpmAtom feed
Upgrading nitropack From 0.2.2 to 2.13.6
125 releases in betweennotes for 70
Reading releases, release notes and advisories…
Counted from 70 of 125 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking2.6.0
- Breaking2.6.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking0.6.0
- Breaking0.6.0
- Breaking0.6.0
- Breaking0.5.0
- Breaking0.5.0
- Breaking0.5.0
Security
Fixes 2 advisories affecting 0.2.2
- Nitro has a proxy scope bypass via percent-encoded path traversal in `routeRules`moderate · GHSA-5w89-w975-hf9q
- Nitro has an Open Redirect via Protocol-Relative URL Bypass in Wildcard Route Rulesmoderate · GHSA-9phm-9p8f-hw5m
- 2.13.6
This release contains 3 security fixes and additional hardening for cache, proxy and redirect route rules.
- 2.13.6
GHSA-39r7-wfcx-99xg: Cached event handlers might share entries across HTTP methods or replay per-user
Set-Cookieheaders - 2.13.6
GHSA-rhhp-7488-3qwf: Proxy route rule scope bypass via empty
//segment and prefix re-entry - 2.13.6
GHSA-pqxc-r4h5-jc95: Open redirect via backslash and control characters in wildcard
redirectroute rules - 2.13.6
route-rules: Prevent open redirect via backslash and control characters in wildcard redirects
- 2.13.4
This release patches two medium-severity vulnerabilities in proxy and redirect route rules.
- 2.13.4
route-rules: Prevent open redirect via protocol-relative url bypass
- 2.13.2
This release upgrades h3 to latest 1.15.9 which contains security fixes.
- 2.13.1
h3@1.15.5released with security fix (release notes)
Release by release
- Security
This release contains 3 security fixes and additional hardening for cache, proxy and redirect route rules.
- Security
GHSA-39r7-wfcx-99xg: Cached event handlers might share entries across HTTP methods or replay per-user
Set-Cookieheaders - Security
GHSA-rhhp-7488-3qwf: Proxy route rule scope bypass via empty
//segment and prefix re-entry - Security
GHSA-pqxc-r4h5-jc95: Open redirect via backslash and control characters in wildcard
redirectroute rules
- Security
- New
aws-amplify: Support node.js 22 and 24 runtimes
- New
vercel: Add framework info to build output config
- New
vercel: Add support for node@24 (v2)
- New
Add missing wrangler observability types
- New
- Security
This release patches two medium-severity vulnerabilities in proxy and redirect route rules.
- Security
route-rules: Prevent open redirect via protocol-relative url bypass
- New
Add version meta
- Fixed
route-rules: Reject out-of-scope requests
- Security
2.13.3nothing new or fixed in the note
- Security
This release upgrades h3 to latest 1.15.9 which contains security fixes.
- New
vercel: Add types and docs for
isr.exposeErrBody - Fixed
prerender: Skip writing routes with
..or outside of public dir - Fixed
prerender: Mark invalid routes as skipped
- Security
- Security
h3@1.15.5released with security fix (release notes)
- Security
- New
vercel: Add support for skew protection
- New
bun: Support
NITRO_BUN_IDLE_TIMEOUTenv variable - New
Process static assets in parallel
- New
Limit concurrency for compressing public assets
- New
- New
vercel: Support bun runtime
- Fixed
Set explicit delimiters to allow $ in replacements
- New
20 other lines we could not sort, mostly version bumps
- 2.13.5
cloudflare: Prefer source path rather than #imports
- 2.13.5
Widen RollupConfig.plugins to accept rolldown-typed plugins
- 2.13.1
unstorage@v1.17.4released withchokidar,lru-cache, andh3dependency bumps (release notes) - 2.11.7
cloudflare: Update node.js compatibility (
node:cryptoandnode:tls) - 2.11.7
netlify-edge: Update node.js compatibility (
node:sqlite) - 2.11.7
- 2.11.5
Mark
$globaloptional forNitroRouteMeta - 2.11.3
Only show force close warn in debug mode
- 2.10.0
.dev(e.g.,server/api/inspect.dev.ts): Included only in development mode. - 2.10.0
.prerender(e.g.,server/api/og_image.prerender.ts): Included only in the prerendering stage.
375 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.