Strapi Release: 4.25.2

TL;DR

Strapi v4.25.2 is a maintenance release that addresses several critical bugs and introduces CLI enhancements. Key fixes include resolving CORS configuration issues, AWS S3 upload compatibility problems, and content manager UI bugs. The release also improves the CLI experience with better authentication flows and removes cloud project creation functionality.

This release is important for maintaining the stability and security of your Strapi applications, particularly if you're using AWS S3 for media storage or experiencing issues with the content manager interface.

Highlight of the Release

• Fixed content manager displayed fields drag-and-drop functionality
• Resolved AWS S3 upload provider compatibility issues
• Added support for string arrays in CORS configuration
• Improved CLI authentication flow with automatic login sequence

Migration Guide

No specific migration steps are required for this patch release. This is a drop-in replacement that fixes bugs and adds minor enhancements.

For general update guidance, refer to the official update guide.

If you're updating from an earlier major version, please consult the migration guides.

Upgrade Recommendations

This patch release (v4.25.2) is highly recommended for all Strapi v4.25.x users, especially for:

• Users experiencing issues with AWS S3 upload provider
• Users having problems with content manager field configuration
• Users working with CORS configurations that include string arrays
• Users of the Patreon OAuth provider in the users-permissions plugin

The update process should be straightforward with minimal risk:

npm install [email protected] [email protected] --save
# or
yarn upgrade [email protected] [email protected]

After updating, restart your Strapi application to apply the changes.

Bug Fixes

Core Fixes

• Content Manager: Fixed an issue where drag-and-drop functionality for displayed fields wasn't working properly (#20613)
• CORS Configuration: Added support for string arrays in CORS configuration (#20658)
• Entity Cloning: Fixed entity cloning functionality (#20531)
• Webhook Security: Prevented use of local IPs on webhooks in production environments (#20487)

Plugin Fixes

• Upload Provider: Updated @aws-sdk/client-s3 package to fix compatibility issues with AWS S3 (#20573)
• Users-Permissions:
  • Fixed a typo in the query key from 'providers' to 'get-providers' (#20034)
  • Added user-agent header to Patreon OAuth requests to prevent 400 errors (#20305)
  • Fixed filters type issue (#20042)

New Features

CLI Improvements

• Enhanced Authentication Flow: The CLI now triggers a login sequence when a token is missing or invalid, providing a smoother experience for developers
• Browser Logout Step: Added a browser logout step to the CLI authentication process
• Simplified Project Creation: Removed the cloud project creation part from the create-strapi-app workflow

Security Updates

Security Enhancements

• Improved webhook security by preventing the use of local IPs in production environments (#20487)
• Added internationalized URL support for better security handling

Performance Improvements

Dependency Updates

• Updated Yarn to version 4.3.1, which brings performance improvements and bug fixes to the package management system

Other Improvements

• Various internal optimizations and code improvements across multiple components

Impact Summary

Strapi v4.25.2 is a maintenance release that addresses several important bugs while introducing minor enhancements to the CLI experience. The fixes span across core functionality and plugins, with particular attention to the content manager UI, AWS S3 integration, and authentication flows.

The most significant impact comes from fixing the AWS S3 upload provider compatibility issue, which was causing problems for users relying on AWS for media storage. Content editors will benefit from the fixed drag-and-drop functionality in the content manager, which improves the content modeling experience.

For developers, the CLI improvements provide a more seamless authentication experience, automatically triggering login when needed. The CORS configuration fix ensures proper handling of string arrays, which is important for applications with complex cross-origin requirements.

This release maintains backward compatibility with previous 4.25.x versions and requires no migration steps, making it a safe and recommended upgrade for all users.

Full Release Notes