-
Notifications
You must be signed in to change notification settings - Fork 115
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
Support for Prisma 6 #475
Comments
Any update about it? |
Unfortunately, this is a significant reason not to use this tool. I understand that the maintainer is not obligated to fix every issue, but this is an important feature. It would be great to leave some tips for anyone with the bandwidth to contribute and help improve it. |
@cesarvspr Please make sure you're up to the statement here: The reality is that I don't use this tool anymore on my daily-basis at work, so I don't have the urge to dedicate my personal time for supporting this project anymore. Prisma abandoned sponsorship some time ago, and the sponsorship was the only reason I started this project. So yes, without a help of community, there's no future for this project. However, maintaining compatibility with new Prisma releases is not so complex, so it shouldn't be an issue to make one or two releases a year. If someone is willing to spend some time on actual digging in the code, fixing the tests after bumping dependencies, feel free to reach me if you need some help, assist or guide. If you only want to yell and complain, there's nothing I can do for you. |
@MichalLytek Thank you for clarifying, and I’m sorry if my message came across the wrong way. I didn’t mean to yell or complain, and I completely understand your situation. My intention was simply to ask if there might be any guidance or information that could help anyone in the community who has the bandwidth to contribute. I truly appreciate the work you’ve put into this project and your willingness to assist others who want to take it forward. |
My workaround for now is overriding the dependencies using prisma 5.22.0: package.json
|
@jbdoster Can you share your whole package.json? I get a duplicate key error Thanks! |
Is your feature request related to a problem? Please describe.
Prisma version 6 has been released, which causes this warning:
Bypassing this warning with
SKIP_PRISMA_VERSION_CHECK=true
works fine for my application, but I don't know if this is the same for everyone.Describe the solution you'd like
For me, just updating the
package.json
version should be enough.Describe alternatives you've considered
Additional context
https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6#breaking-changes
The text was updated successfully, but these errors were encountered: