- Shipped
- September 16, 2026 at 10:06 PM UTC
- Author
- Kamo
- Commit
- 571e248
Entry pages failed in bursts while services rolled out: SecurityService answered 500 for a database schema-version bump or dropped the connection while restarting, and the first failed read threw straight to the framework's bare error screen. - getChangelogEntry tries a 5xx or a dropped connection three times before giving up, then throws ChangelogUnavailableError. A 404 is still a 404. - generateMetadata no longer rethrows that failure; the page does. - error.tsx beside the entry page shows where the reader is, that it is temporary, and offers Try again and All changes. The response stays a 500 so crawlers retry instead of dropping the address.