New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to "prisma": "4.6.1"
#4062
Conversation
🦋 Changeset detectedLatest commit: db3d23e The changes in this PR will be included in the next version bump. This PR includes changesets to release 7 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Looking through the release log https://github.com/prisma/prisma/releases from 4.6 to the current 4.9 I don't see any breaking changes. I wonder if Blitz should update to |
fe70a31
to
0b0af99
Compare
@tordans - Prisma released Version 4.9.0 - maybe we should use this version directly? |
This is just a minor change to address the enum bug. I did not test anything else... |
@siddhsuresh I applied you code review; let me know if there is anything else – thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
make that change to the changelog, otherwise good to go :)
lastly can you resolve the pnpm lock conflict? :) |
Update Prisma from `4.6.0` to `4.6.1` to solve enum issue with PostgreSQL prisma/prisma#16180
Co-Authored-By: Brandon Bayer <b@bayer.ws> Co-Authored-By: Siddharth Suresh <siddh.suresh@gmail.com>
f635bd3
to
6f76519
Compare
@flybayer I rebased and resolved the conflicts and ran & checked in |
Closes: -
What are the changes and their implications?
Update Prisma from
4.6.0
to4.6.1
to solve enum issue with PostgreSQL prisma/prisma#16180Feature Checklist
pnpm changeset
in the root directory)main
branch)