TL;DR
Strapi v5.0.0-beta.11: Client Router API, Content Releases Migration, and UI Fixes
This beta release introduces a new client router API, completes the migration of Content Releases to v5, and addresses several UI issues including date picker timezone problems and pagination styling. It also enhances proxy configuration with a global HTTP/HTTPS proxy setting and fixes multiple media handling. This release continues to stabilize the v5 platform with important bug fixes and developer experience improvements.
Highlight of the Release
- New client router API for more flexible routing options
- Complete migration of Content Releases feature to v5
- Fixed date picker timezone issues that caused UI jumping
- Enhanced global HTTP/HTTPS proxy configuration
- Improved database migration logging with Umzug upgrade
Migration Guide
Breaking Changes
Global HTTP/HTTPS Proxy Configuration
The way global HTTP/HTTPS proxies are configured has changed. Now you should use the server.globalProxy value for creating a global HTTP/HTTPS proxy. If you were using proxy configuration in your Strapi application, you'll need to update your configuration to use this new approach.
Multiple Media Configuration
The "multiple" option for media fields is now only available in attribute configuration. If you were configuring multiple media in other locations, you'll need to update your code to reflect this change.
Content Releases Migration
If you were using Content Releases in v4, this release includes migration support to ensure your data is properly migrated to the v5 structure. The migration handles the relation between actions and documents automatically.
Upgrade Recommendations
As this is still a beta release (v5.0.0-beta.11), it's recommended for testing and development environments only. If you're already using v5.0.0-beta.10, upgrading to this version is recommended to benefit from the bug fixes and improvements.
For production environments, it's advised to wait for the stable v5.0.0 release. However, if you're actively developing with v5 beta, this update includes important fixes and enhancements that improve the overall stability and user experience.
Pay special attention to the breaking changes related to global proxy configuration and multiple media handling if these features are used in your application.
Bug Fixes
UI and Interaction Fixes
- Fixed date picker component that was jumping around due to timezone issues
- Added bottom padding to pagination component for better visual appearance
- Fixed draft and publish toggle in the Content-Type Builder
- Fixed the Time field format on saving
- Fixed Content Releases validation and dropdown menu endIcon
- Fixed SQLite default config filename that was missing
Content Management Fixes
- Fixed multiple media handling - "multiple" is now only available in attribute configuration
- Fixed Content Releases relation between actions and documents
- Fixed Content Releases menu button and UI elements
New Features
Client Router API
A new client router API has been added, providing more flexible routing options for developers. This includes an addRoute method to the router class, making it easier to define and manage routes in your Strapi applications.
Content Releases Settings
Content Releases now includes settings functionality, allowing administrators to configure release behavior. This includes timezone settings and appropriate permissions management for different user roles.
Security Updates
No specific security fixes were mentioned in this release.
Performance Improvements
Database and Migration Improvements
- Upgraded Umzug dependency and improved database migration logging, making it easier to track and debug migration processes
- Added Ajv to dependencies as a patch to improve validation performance
Impact Summary
This beta release represents significant progress in stabilizing Strapi v5 with important feature additions and bug fixes. The new client router API enhances developer flexibility, while the completion of Content Releases migration to v5 brings this enterprise feature fully into the v5 ecosystem.
The UI fixes address several pain points reported by users, particularly the date picker timezone issue that caused visual jumping. The improved database migration logging will help developers troubleshoot migration issues more effectively.
The breaking changes around global proxy configuration and multiple media handling are relatively minor but require attention during upgrade. Overall, this release continues to refine the v5 experience with a focus on stability, developer experience, and UI improvements.
For teams already working with v5 beta, this update provides valuable fixes and enhancements that make the platform more reliable and user-friendly.
