Prisma v8.0.0-rc.21: Breaking Changes
- Investigating(current)
- Trending(upcoming)
- Workaround available(upcoming)
- Resolved(upcoming)
Executive summary
The upgrade to prisma v8.0.0-rc.21 introduces breaking changes, including a change in how client members return results (promises or results) and the use of supabase(). After upgrading, run prisma contract emit once.
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
2 reports · 2 GitHubShow
- [1]GitHub First reportprisma/prisma v8.0.0-rc.21: breaking changes(opens GitHub issue in a new tab)
The upgrade recipes for this hop: the app recipe and the extension recipe. Each breaking change below names the change ids to look for in them. After upgrading, run prisma contract emit once, so a contract that an extension such as Supabase stamps with its version matches the installed package (contract-artifacts-restamp in the app recipe). Breaking changes A client member that returns a promise or a result rejects instead of throwing at the call. On postgres(), sqlite(), a supabase()…
by wmadden-electric 1upvotes 0comments
- [2]GitHubprisma/prisma v8.0.0-rc.22: breaking changes(opens GitHub issue in a new tab)
The upgrade recipes for this hop: the app recipe and the extension recipe. Each breaking change below names the change ids to look for in them. The app recipe opens with the order to do the steps in. After upgrading, run prisma contract emit once, so a contract that an extension such as Supabase stamps with its version matches the installed package (contract-artifacts-restamp in the app recipe). Breaking changes On PostgreSQL, DateTime, Date and Time are convenience types with new defaults.…
by github-actions[bot] 5upvotes 0comments97% match
Timeline
- First report on GitHub issue
prisma/prisma v8.0.0-rc.21: breaking changes
Source