feat(db-mongodb)!: update mongoose to 8.8.1#9115
Merged
Merged
Conversation
Member
From https://www.npmjs.com/package/mongoose-paginate-v2 removing |
596cfcd to
7d94618
Compare
BREAKING CHANGES: For projects making use of the exposed Models from mongoose, review the upgrade guides from [v6 to v7](https://mongoosejs.com/docs/7.x/docs/migrating_to_7.html) and [v7 to v8](https://mongoosejs.com/docs/migrating_to_8.html) and make adjustments as needed.
77f94be to
2025702
Compare
- Adds predefined migration `@payloadcms/db-mongodb/relationships-v2-v3` that converts all string relationship values to ObjectIDs. - Fixes / refactors `versions-v1-v2` migration, ensures the transaction is used - Adds tests for Mongoose predefined migrations
156e2fc to
8da019e
Compare
214f961 to
b553a25
Compare
b553a25 to
01fea15
Compare
Contributor
|
🚀 This is included in version v3.0.0-beta.131 |
kendelljoseph
pushed a commit
that referenced
this pull request
Feb 21, 2025
### What? Upgrades mongoose from 6 to latest `v8.8.1` Fixes #9171 ### Why? Compatibilty with Mongodb Atlas ### How? - Updates deps - Changed ObjectId from bson-objectid to use `new Type.ObjectId` from mongoose for compatibility (only inside of db-mongodb) - Internal type adjustments #9088 BREAKING CHANGES: All projects with existing data having versions enabled, or relationship or upload fields will want to create the predefined migration that converts all strings to ObjectIDs where needed. This can be created using `payload migrate:create --file @payloadcms/mongodb/relationships-v2-v3`. For projects making use of the exposed Models from mongoose, review the upgrade guides from [v6 to v7](https://mongoosejs.com/docs/7.x/docs/migrating_to_7.html) and [v7 to v8](https://mongoosejs.com/docs/migrating_to_8.html) and make adjustments as needed. --------- Co-authored-by: Sasha <64744993+r1tsuu@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Upgrades mongoose from 6 to latest
v8.8.1Fixes #9171
Why?
Compatibilty with Mongodb Atlas
How?
new Type.ObjectIdfrom mongoose for compatibility (only inside of db-mongodb)#9088
BREAKING CHANGES:
All projects with existing data having versions enabled, or relationship or upload fields will want to create the predefined migration that converts all strings to ObjectIDs where needed.
This can be created using
payload migrate:create --file @payloadcms/mongodb/relationships-v2-v3.For projects making use of the exposed Models from mongoose, review the upgrade guides from v6 to v7 and [v7 to v8 (https://mongoosejs.com/docs/migrating_to_8.html) and make adjustments as needed.