vercel/next.js v16.5.0-canary.39 Regression Fix
- Investigating(current)
- Trending(upcoming)
- Workaround available(upcoming)
- Resolved(upcoming)
Executive summary
A regression fix has been released for vercel/next.js version 16.5.0-canary.39, which includes tests to ensure parity with Segment and fixes for flaky resume data cache tests.
No verified workaround yet
None of the linked reports describe a mitigation. Follow this incident to hear when one appears.
Official fixUnder active investigation. No report has identified a root cause yet.
Evidence
1 report · 1 GitHubShow
- [1]GitHub First reportvercel/next.js v16.5.0-canary.39: regression fix(opens GitHub issue in a new tab)
Add segment config parity regression tests: #100881 Turbopack: cleanup ReferencedAssetIdent: #101095 [test] Fix flaky resume data cache tests: #101088 docs: fix import.meta.glob base docs: #101085 create-next-app: remove unused webpack bundler option: #101081 [experiment] [turbopack-cli] compile .go files: #99980 Credits Huge thanks to @eps1lon, @lukesandberg, @mischnic, @unstubbable, @icyJoseph, and @timneutkens for helping!
by next-js-bot[bot] 1upvotes 0comments
Timeline
- First report on GitHub issue
vercel/next.js v16.5.0-canary.39: regression fix
Source