Strapi Release: 4.14.2

TL;DR

Strapi v4.14.2 is a maintenance release that addresses NPM publishing issues from the previous version. No functional changes were made to the codebase, but this release ensures proper package availability on NPM. Users who experienced installation or dependency resolution problems with v4.14.0 should upgrade to this version.

Highlight of the Release

• Fixed NPM publishing issues that affected package availability
• No functional code changes from v4.14.0

Migration Guide

No migration is required when upgrading from v4.14.0 to v4.14.2 as there are no functional changes to the codebase. Simply update your package.json dependencies to use the new version:

npm install @strapi/[email protected] --save

Or if using Yarn:

yarn upgrade @strapi/[email protected]

Upgrade Recommendations

Users currently on v4.14.0 should upgrade to v4.14.2 to ensure they have properly published packages. This is especially important if you've experienced any NPM-related installation issues.

For users on earlier versions (pre-4.14.0), you should review the v4.14.0 changelog first to understand the functional changes introduced in that version before upgrading to v4.14.2.

Bug Fixes

This release fixes NPM package publishing issues that affected v4.14.0. The fix ensures that all Strapi packages are properly published and available on the NPM registry, resolving installation and dependency resolution problems that some users may have encountered.

New Features

No new features were introduced in this release. This is strictly a maintenance release to address NPM publishing issues with the previous v4.14.0 release.

Security Updates

No security fixes were included in this release. This is strictly a maintenance release to address NPM publishing issues.

Performance Improvements

No performance improvements were included in this release as it contains no functional code changes from v4.14.0.

Impact Summary

This release has minimal impact on existing Strapi installations as it contains no functional changes. The primary impact is on the installation and dependency resolution process through NPM, which should now work correctly.

For teams that were blocked from upgrading to v4.14.0 due to NPM issues, this release provides a path forward to access the features and improvements introduced in the v4.14.x line without the packaging problems.

No changes to application code, database structures, or APIs were made in this release.

Full Release Notes