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.

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

Prisma v5 support #8117

Closed
overbit opened this issue Feb 24, 2024 · 1 comment · Fixed by #8118
Closed

Prisma v5 support #8117

overbit opened this issue Feb 24, 2024 · 1 comment · Fixed by #8118
Assignees
Labels
impact: Quality initiatives that focus on ensuring the quality of the product type: dependencies Pull requests that update a dependency file type: perf A code change that improves performance type: tech-debt

Comments

@overbit
Copy link
Contributor

overbit commented Feb 24, 2024

Feature description

Amplication generated code already support prisma v5 as it comes with many improvements especially regarding the client performance.
To improve the amplication SAAS performance, monorepo should be migrated to v5 too.

Use case

No response

Are you willing to submit PR?

Yes I am willing to submit a PR!

@overbit overbit added type: dependencies Pull requests that update a dependency file type: perf A code change that improves performance type: tech-debt impact: Quality initiatives that focus on ensuring the quality of the product labels Feb 24, 2024
@overbit overbit self-assigned this Feb 24, 2024
@overbit overbit linked a pull request Feb 24, 2024 that will close this issue
2 tasks
@mulygottlieb
Copy link
Member

Passed QA - Prisma was updated to v5 and the system is running and passing sanity.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact: Quality initiatives that focus on ensuring the quality of the product type: dependencies Pull requests that update a dependency file type: perf A code change that improves performance type: tech-debt
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants