🐛 Bug fix
- [core:database] Fix undefined pk (#8260) @alexandrebodin
- [plugin:upload] Update index.js (#8242) @laurenskling
Tag Name: v3.2.3
Release Date: 10/9/2020
StrapiOpen-source headless CMS built with Node.js. Provides developers with complete freedom in choosing their favorite tools and frameworks for frontend development.
Strapi v3.2.3 is a maintenance release that fixes two critical bugs: one related to undefined primary keys in the database module and another addressing a TypeError in the upload plugin. These fixes improve the stability of the platform for developers working with database operations and file uploads.
No migration steps are required for this release as it only contains bug fixes that don't introduce breaking changes.
For general migration guidance between Strapi versions, please refer to the official migration guides.
This release contains important bug fixes that improve stability. All users of Strapi v3.2.2 should upgrade to v3.2.3, especially if you:
To upgrade, run one of the following commands depending on your package manager:
npm install [email protected] --save
or
yarn upgrade [email protected]
Database Module: Fixed an issue with undefined primary keys that could cause errors during database operations (#8260)
Upload Plugin: Fixed a TypeError: Cannot read property 'message' of undefined by improving error handling in the upload plugin. The fix now uses error.message directly instead of trying to access the non-existent error.error.message property (#8242)
No new features were introduced in this release as it focuses exclusively on bug fixes.
No security fixes were included in this release.
No specific performance improvements were included in this release.
This is a minor bug fix release that addresses two specific issues without introducing any breaking changes. The fixes resolve potential errors that could occur during database operations with undefined primary keys and improve error handling in the upload plugin. These changes enhance the overall stability of Strapi v3.2.x for developers and content managers working with the platform.
The impact is primarily positive for users who may have encountered these specific errors, providing a more stable experience without requiring any migration steps or workflow changes.