What's Changed
- fix: issue 20138 by @alexandrebodin in #20231
Full Changelog: v4.23.1...v4.23.2
Tag Name: v4.23.2
Release Date: 5/1/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 v4.23.2 is a patch release that fixes a critical issue (#20138) affecting the CMS functionality. This release ensures proper operation of the Strapi CMS by addressing a specific bug that was introduced in the previous version.
No migration steps are required for this patch release. Users can update from v4.23.1 to v4.23.2 without any special migration procedures.
To update your Strapi instance:
# Using npm
npm install [email protected] --save
# Using Yarn
yarn upgrade [email protected]
# Using pnpm
pnpm update [email protected]
After updating, restart your Strapi application to apply the fix.
It is highly recommended to upgrade to v4.23.2 if you are currently using v4.23.1, especially if you have encountered issue #20138. This patch release specifically addresses this issue and improves the stability of your Strapi instance.
The upgrade is straightforward with no breaking changes, making it a low-risk update that provides immediate benefits in terms of stability and functionality.
While the specific details of the issue are not fully described in the commit messages, this patch addresses a bug that was significant enough to warrant a dedicated patch release.
This patch release does not introduce any new features as it is focused solely on fixing a specific issue (#20138).
No security fixes were explicitly mentioned in this release. The patch appears to be focused on functional bug fixes rather than addressing security vulnerabilities.
No specific performance improvements were mentioned in this release. The focus was on fixing a bug rather than enhancing performance.
This patch release has a targeted impact on Strapi installations affected by issue #20138. While the specific details of the issue are not elaborated in the commit messages, the fact that it warranted a dedicated patch release suggests it was a significant bug affecting core functionality.
The changes in this release are substantial in terms of code modifications (596 additions, 380 deletions across 50 files), indicating that the fix required comprehensive changes to resolve the issue properly.
Users who have experienced problems related to issue #20138 will benefit immediately from this update, with no migration effort required. The release maintains compatibility with existing Strapi installations and focuses solely on fixing the identified bug without introducing new features or breaking changes.
Full Changelog: v4.23.1...v4.23.2