-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
ci: Setup pnpm catalog to centralize depedency versions (no-changelog) #9974
Conversation
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.
Nice 👍 Just one Q about how to categorize the catalogs
'@types/basic-auth': ^1.1.3 | ||
'@types/express': ^4.17.21 |
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.
Some of these are used only in the backend packages. Should we have a separate backend
catalog like we have one for frontend?
✅ All Cypress E2E specs passed |
Test summaryRun details
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Cloud |
Got released with |
Summary
pnpm 9.5 added a new feature called catalog that helps organize dependency versions in a centralized location, to help maintain consistent versions of dependencies and to make upgrading duplicated dependencies easier.
Review / Merge checklist