Skip to content
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.

Sign up for GitHub

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

Jump to bottom

prisma version mismatch #1122

Closed
malteish opened this issue Jul 19, 2024 · 2 comments · Fixed by #1143
Closed

prisma version mismatch #1122

malteish opened this issue Jul 19, 2024 · 2 comments · Fixed by #1143
Assignees
@malteish
Labels
do not merge check description for reason

Comments

@malteish
Copy link
Collaborator

malteish commented Jul 19, 2024 •
edited
Loading

When building the backend, I see this warning:
warn Versions of [email protected] and @prisma/[email protected] don't match.

The mismatch comes from package.json.

I believe we should fix it.
@malteish
Copy link
Collaborator Author

Upgrade guide: https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-5

@malteish malteish mentioned this issue Aug 12, 2024
Closed
@malteish malteish self-assigned this Aug 12, 2024
@malteish malteish mentioned this issue Aug 12, 2024
Merged
@malteish malteish added the do not merge check description for reason label Aug 15, 2024
@malteish
Copy link
Collaborator Author

Do not merge before #1091 has been completed by me. I don't want to mix 2 changes to the database infrastructure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@malteish malteish

Labels
do not merge check description for reason
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Sync prisma versions dm3-org/dm3
update and sync prisma packages dm3-org/dm3
2 participants
@AlexNi245 @malteish