What's Changed
- fix: delete orphan component data when schema changes by @innerdvations in #22664
- fix: disable lifecycle hooks on transfers [v4] by @Bassel17 in #22650
Full Changelog: v4.25.19...v4.25.20
Tag Name: v4.25.20
Release Date: 1/22/2025
StrapiOpen-source headless CMS built with Node.js. Provides developers with complete freedom in choosing their favorite tools and frameworks for frontend development.
This maintenance release addresses two important bugs in Strapi CMS:
These fixes improve data consistency and transfer reliability for Strapi administrators and developers.
No migration steps are required for this release. The fixes are applied automatically when upgrading to v4.25.20.
However, if you've implemented custom solutions to work around the fixed issues (such as manual cleanup of orphaned component data or custom handling of lifecycle hooks during transfers), you may want to review and potentially remove those workarounds after upgrading.
This release is recommended for all Strapi users, especially those who:
The upgrade should be straightforward with no breaking changes:
npm install [email protected]
# or
yarn upgrade [email protected]
After upgrading, no additional configuration changes are required to benefit from the fixes.
No new features were introduced in this release. This is primarily a bug fix release focused on improving data consistency and transfer reliability.
No security fixes were included in this release. The changes focus on bug fixes related to data integrity and transfer operations.
No specific performance improvements were highlighted in this release. The changes focus on bug fixes related to data integrity and transfer operations rather than performance enhancements.
This release focuses on improving data integrity and reliability in Strapi CMS. By fixing the orphaned component data issue, it prevents potential data inconsistencies that could occur after schema changes. The disabling of lifecycle hooks during transfers ensures more predictable and reliable data transfer operations.
These changes are particularly important for production environments where data integrity is critical. Administrators and developers will benefit from more reliable schema changes and transfer operations without having to implement manual workarounds.
While these changes don't introduce new features or visible improvements to the user interface, they strengthen the foundation of Strapi's data management capabilities, which is essential for a robust content management system.
Full Changelog: v4.25.19...v4.25.20