Next.js release checklist for small apps
A compact release checklist for static-first Next.js apps that still expose dynamic utility endpoints.
Takeaway
Small apps still need boring release gates: deterministic builds, route checks, cache expectations, environment review, and rollback notes.
01
Verify the generated surface
Run lint, tests, and a production build before release, then read the route output. Static pages, dynamic endpoints, image routes, sitemap, robots, and manifest routes should match what the public navigation and README claim is live.
02
Check operational assumptions
Review environment variables, response caching, request limits, and sensitive-data boundaries before deploying. Utility apps should be especially careful not to log pasted payloads, decoded claims, or raw request bodies unnecessarily.
03
Write down rollback signals
Before launch, define the symptoms that would trigger rollback: broken core tools, failing API endpoints, incorrect metadata routes, or a build that publishes stale content. Keep the rollback command close to the release note.