What's Changed
fix: v5 migration with wrong enum values by @Marc-Roig #21588
Full Changelog: v5.0.2...v5.0.3
Tag Name: v5.0.3
Release Date: 10/7/2024
StrapiOpen-source headless CMS built with Node.js. Provides developers with complete freedom in choosing their favorite tools and frameworks for frontend development.
Strapi v5.0.3 fixes a critical issue with the v5 migration process where enum values were being incorrectly handled. This patch ensures that content types with enum attributes migrate properly from v4 to v5, preventing potential data loss or corruption during the upgrade process.
No specific migration steps are required for this patch release.
If you were experiencing issues with enum values during migration from v4 to v5, upgrading to v5.0.3 should resolve these problems. After upgrading, you may need to re-run your migration if it previously failed due to this issue.
For users who have already migrated but encountered enum-related data issues, you may need to review your content types with enum attributes to ensure data integrity.
This is a highly recommended upgrade for all users who:
The fix addresses a specific migration issue that could lead to data corruption, so upgrading is important for maintaining data integrity during the migration process.
To upgrade from v5.0.2 to v5.0.3:
npm install [email protected]
or
yarn upgrade [email protected]
This release addresses a critical issue in the v5 migration process where enum values were being incorrectly handled. The bug caused problems when migrating content types with enum attributes from Strapi v4 to v5, potentially resulting in data corruption or failed migrations.
The fix ensures that enum values are properly processed during migration, maintaining data integrity when upgrading from v4 to v5.
No new features were added in this release. This is a bug fix release focused on addressing migration issues.
No security fixes were included in this release.
No specific performance improvements were included in this release. The focus was on fixing the migration issue with enum values.
This release has a moderate impact focused specifically on the migration process from Strapi v4 to v5. It fixes a critical issue with enum values during migration that could lead to data corruption or failed migrations.
The fix is particularly important for users with content types that include enum attributes, as these were the most affected by the bug. By addressing this issue, Strapi ensures a smoother upgrade path from v4 to v5, reducing the risk of data problems and eliminating the need for manual intervention or workarounds.
While this is a small patch in terms of code changes, it has significant implications for data integrity during the migration process, making it an important update for anyone planning to upgrade from v4 to v5.
fix: v5 migration with wrong enum values by @Marc-Roig #21588
Full Changelog: v5.0.2...v5.0.3