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

Is there any guide that reference the breaking changes for each new v3 release ? #10512

Open
LeoAnt02 opened this issue Jan 11, 2025 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@LeoAnt02
Copy link

LeoAnt02 commented Jan 11, 2025

Documentation Issue

Upgrading from 3.1 to 3.16 cause a few issues, mongoose errors at runtime, payload command errors on cli

from

 "@payloadcms/db-mongodb": "^3.1.0",
"@payloadcms/live-preview-react": "^3.1.0",
"@payloadcms/next": "^3.1.0",
"@payloadcms/payload-cloud": "^3.1.0",
"@payloadcms/plugin-form-builder": "^3.1.0",
"@payloadcms/plugin-nested-docs": "^3.1.0",
"@payloadcms/plugin-redirects": "^3.1.0",
"@payloadcms/plugin-search": "^3.1.0",
"@payloadcms/plugin-seo": "^3.1.0",
"@payloadcms/richtext-lexical": "^3.1.0",
"@payloadcms/ui": "^3.1.0",
"payload": "^3.1.0",

to

"@payloadcms/db-mongodb": "^3.16.0",
"@payloadcms/live-preview-react": "^3.16.0",
"@payloadcms/next": "^3.16.0",
"@payloadcms/payload-cloud": "^3.16.0",
"@payloadcms/plugin-form-builder": "^3.16.0",
"@payloadcms/plugin-nested-docs": "^3.16.0",
"@payloadcms/plugin-redirects": "^3.16.0",
"@payloadcms/plugin-search": "^3.16.0",
"@payloadcms/plugin-seo": "^3.16.0",
"@payloadcms/richtext-lexical": "^3.16.0",
@LeoAnt02 LeoAnt02 added the documentation Improvements or additions to documentation label Jan 11, 2025
@jacobsfletch
Copy link
Member

What errors are you experiencing? We follow a strict semver policy where there should be no breaking changes between minor and patch versions. Breaking changes will only occur in major releases. It's possible your package manager has installed mismatching versions across the various packages due to the caret operator in your package.json. You can verify this by inspecting your project's lock file. I'm also not seeing payload itself or @payloadcms/ui defined in the second snippet you provided. Did you omit those intentionally? Everything needs to match as these packages rely on each other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants