Add 4.5.1 migration preparation step #1345
Merged
Conversation
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
Marc-Roig
added
source: Dev Docs
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Marc-Roig
changed the title
Marc-Roig
changed the title
|
This pull request has been mentioned on Strapi Community Forum. There might be relevant details there: https://forum.strapi.io/t/new-documentation-release-v4-5-5/24573/1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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 does it do?
As specified in the migration document name (v4.4.5 to v4.5.1 migration guide), The 4.5.X migration script is supposed to work when the app is migrating from versions older than 4.4.X.
Some users were updating from older versions and having errors that were not pointing to what the problem was.
strapi/strapi#14978
I did not find a way to look at which version the user is updating, so I think the best solution is to explain this in the migration preparation steps.
Why is it needed?
So users know they have to update from versions older than 4.4.X.
Related issue(s)/PR(s)
strapi/strapi#14978