TL;DR
Strapi v5.0.0-rc.9 brings important UI improvements with Design System updates, fixes for relation handling in the Content Manager, and introduces RBAC action aliases. This release also includes workflow improvements, bug fixes for E2E tests, and standardization of registry data types, making the platform more stable as it approaches the final v5 release.
Highlight of the Release
- Design System updated to RC-7 with numerous UI improvements and style fixes
- RBAC Action Aliases introduced for more flexible permission management
- Fixed relation handling to properly load main fields on all pages
- Standardized policy registry to return same data types as other registries
Migration Guide
No specific migration steps are required for this release candidate update. As this is a pre-release version (RC-9), users should be aware that further changes may occur before the final v5.0.0 release.
If you're upgrading from RC-8 to RC-9, the process should be straightforward:
npm install @strapi/[email protected]
or
yarn add @strapi/[email protected]
Note that internal dependencies now use workspace:* versioning, which should simplify dependency management for those working with the Strapi codebase directly.
Upgrade Recommendations
As this is a release candidate (RC-9), it's recommended for:
- Developers actively testing Strapi v5 features
- Contributors to the Strapi project who want to help identify and fix issues before the final release
- Teams preparing their applications for the upcoming v5 stable release
This is not recommended for production environments unless you're comfortable with potential breaking changes in future release candidates or the final v5 release.
If you're currently using RC-8, upgrading to RC-9 is recommended to benefit from the latest bug fixes and UI improvements.
Bug Fixes
Content Manager Relation Fixes
- Fixed relation handling in the Content Manager to properly load relation main fields on all pages, ensuring consistent data display across the admin interface.
Registry Consistency
- Fixed policies registry to return the same data types as other registries, ensuring consistent behavior across the application.
Database Ordering
- Added
columnName to order column attributes, fixing issues with relations for shortened contentTypes.
E2E Test Fixes
- Fixed failing E2E tests to ensure proper test coverage and reliability.
UI Component Fixes
- Fixed various styling issues:
- Adjusted grid item styles
- Updated Add to Dynamic Zone button styling
- Removed fieldset border width
- Updated popover menu icon colors
- Fixed WYSIWYG expand/collapse button styles
- Centered "more" button icon
- Fixed main navigation icon sizes
- Improved help button styling
- Fixed email settings button
New Features
RBAC Action Aliases
The release introduces RBAC Action Aliases, allowing for more flexible and intuitive permission management. This feature enables administrators to create aliases for actions, making permission configuration more user-friendly and adaptable to specific use cases.
Design System Improvements
The Design System has been updated to RC-7, bringing numerous UI enhancements:
- Improved styling for Dynamic Zone components and buttons
- Updated color picker interface
- Enhanced WYSIWYG editor expand/collapse functionality
- Better icon sizing and positioning in the main navigation
- Improved help button styling
- Fixed email settings button appearance
Security Updates
No security fixes were explicitly mentioned in this release.
Performance Improvements
No specific performance improvements were highlighted in this release. The focus appears to be on UI enhancements, bug fixes, and feature additions rather than performance optimizations.
Impact Summary
Strapi v5.0.0-rc.9 represents another step toward the stable v5 release, focusing on UI refinements, bug fixes, and developer experience improvements. The Design System updates enhance the overall look and feel of the admin interface, while fixes to relation handling in the Content Manager address important functionality issues.
The introduction of RBAC Action Aliases provides more flexibility for permission management, which will be particularly valuable for complex applications with nuanced access control requirements.
For developers, the standardization of registry data types and the move to workspace:* versioning for internal dependencies reflect Strapi's commitment to a more consistent and maintainable codebase.
This release candidate continues to stabilize the v5 platform, making it more robust for early adopters while preparing for the eventual stable release.
