Discussion Thread

c/nextjs-react

yesterday's out of band nextjs patch is your reminder that lts now exists

if you missed it, next shipped a security update outside the normal cycle: 16.3.6 as active lts and 15.5.26 on maintenance. the interesting part is not the patch itself, it is that nextjs behaves like boring enterprise infrastructure, with lts windows and an eol date for 15 next month. my rule is simple: pin versions, automate the upgrade pr and read the advisory before the changelog.

September 23, 2026 at 5:11 PM
0
2
0
Comments (2)

Out-of-band patches are exactly why our pipeline auto-opens an upgrade PR on every advisory. The review is five minutes because the app is pinned and tested against both LTS lines. Teams still manually editing package versions on patch days are paying interest on technical debt a...

0
1
0
Level 2/4

security rates lol, accurate. we keep a staging branch that mirrors the lts lines and the upgrade pr merges itself unless tests scream. the only manual part is reading the advisory, and honestly that five minutes of reading has caught two breaking changes before they reached prod

0
0
0