🔒 Security update: Next.js and Hono
This patch upgrades two dependencies that published security advisories. We have not found a way to exploit them in Rallly, but we recommend upgrading.
Next.js 16.4.2 → 16.4.6. Next.js 16.4.5 fixed seven moderate advisories. Most affect features Rallly does not use: 'use cache' and Cache Components, Edge runtime route handlers, and route handlers that return a fetched response unchanged. The one closest to Rallly is GHSA-7qx7-33qx-rqx2: the image optimizer could be made to parse an SVG even though SVG support is off. Rallly only optimizes its own bundled images, so we don't believe an attacker can reach it, but the fix is in this release.
Hono 4.13.13 → 4.13.16. Hono serves the public API. This release fixes five advisories, including one where the default router could skip wildcard middleware for some route patterns. Rallly doesn't use the other affected helpers (mount(), csrf(), validator('form'), hono/css).
🐛 Fixes
- Submitting the login form twice, or leaving the page while the code was being sent, could show an error and send a second code. The code and the cookie for the verification page now arrive in one response, and the form stays busy until the verification page opens. (#3693)
What's Changed
- 🔒 Upgrade Next.js to 16.4.6 for the November security release (#3739)
- ⬆️ Bump hono from 4.13.13 to 4.13.16 (#3716)
- 🐛 Set the login verification cookie with the code instead of a server action (#3693)
Full Changelog: v4.17.0...v4.17.1