Home

>

Tools

>

Strapi

>

Releases

>

4.25.20

Strapi Release: 4.25.20

Tag Name: v4.25.20

Release Date: 1/22/2025

Strapi LogoStrapi

Open-source headless CMS built with Node.js. Provides developers with complete freedom in choosing their favorite tools and frameworks for frontend development.

TL;DR

Strapi v4.25.20 Release

This maintenance release addresses two important bugs in Strapi CMS:

  1. Fixed an issue where orphaned component data remained in the database after schema changes, which could lead to data inconsistencies.
  2. Disabled lifecycle hooks during data transfers to prevent unintended side effects and ensure data integrity during transfer operations.

These fixes improve data consistency and transfer reliability for Strapi administrators and developers.

Highlight of the Release

    • Fixed deletion of orphaned component data when schema changes
    • Disabled lifecycle hooks during transfer operations to prevent unintended side effects

Migration Guide

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.

Upgrade Recommendations

This release is recommended for all Strapi users, especially those who:

  • Frequently modify component schemas in their Strapi applications
  • Use data transfer operations between environments or for backup/restore purposes

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.

Bug Fixes

Orphaned Component Data Cleanup

  • Fixed an issue where component data would remain in the database as orphaned records after schema changes (#22664)
  • Previously, when modifying component schemas, related data could become orphaned and remain in the database, potentially causing inconsistencies
  • The fix ensures proper cleanup of these orphaned records, maintaining data integrity

Lifecycle Hooks During Transfers

  • Fixed an issue where lifecycle hooks would execute during data transfer operations (#22650)
  • Previously, these hooks could trigger unintended side effects during transfers
  • The fix disables lifecycle hooks specifically during transfer operations, ensuring more predictable and reliable transfers

New Features

No new features were introduced in this release. This is primarily a bug fix release focused on improving data consistency and transfer reliability.

Security Updates

No security fixes were included in this release. The changes focus on bug fixes related to data integrity and transfer operations.

Performance Improvements

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.

Impact Summary

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 Release Notes

Statistics:

File Changed68
Line Additions1,194
Line Deletions428
Line Changes1,622
Total Commits8

User Affected:

  • Benefit from improved data consistency when making schema changes to components
  • Experience more reliable data transfers without unexpected side effects from lifecycle hooks

Contributors:

innerdvationsBassel17Marc-Roig