Strapi Release: 5.0.0-rc.20

TL;DR

Strapi v5.0.0-rc.20 is a release candidate that focuses on bug fixes and improvements to the developer experience. This update addresses several UI and functionality issues, including fixes for date/time formatting, template configurations, and property naming conventions. These changes improve the reliability and usability of Strapi's admin interface and developer templates, making it more stable as it approaches the final v5.0.0 release.

Highlight of the Release

• Fixed single type fill from locale functionality
• Improved date and datetime value formatting
• Fixed JavaScript example templates and Vite configuration
• Enhanced sorting for complex data types using mainField name
• Standardized property naming using documentId instead of id

Migration Guide

No migration steps are required for this release candidate. The changes are primarily bug fixes that don't require manual intervention when upgrading from v5.0.0-rc.19.

If you're using custom code that relies on the id property that was changed to documentId, you may need to update your code accordingly.

Upgrade Recommendations

If you're already using Strapi v5.0.0-rc.19, it's recommended to upgrade to v5.0.0-rc.20 to benefit from the bug fixes and improvements, especially if you're experiencing any of the issues addressed in this release.

This is a release candidate, so it's suitable for testing and development environments. For production environments, consider waiting for the final v5.0.0 release unless you specifically need these fixes.

To upgrade:

npm install [email protected]

or

yarn add [email protected]

Bug Fixes

UI and Data Handling Fixes

• Fixed single type fill from locale functionality that was previously disabled (#21200)
• Fixed the value format on change for date and datetime fields to ensure consistent data handling (#21197)
• Resolved default time formatting issues for better display in the admin interface (#21206)
• Fixed header name property to use the mainField name for complex data types like stage and assignee, improving sorting functionality (#21198)

Template and Configuration Fixes

• Fixed JavaScript example templates to provide better developer experience (#21205)
• Fixed Vite configuration examples in templates to ensure proper functionality (#21204)
• Updated property naming to use documentId instead of id for more consistent API interactions (#21200)

New Features

No new features were introduced in this release candidate. This update focuses on bug fixes and improvements to existing functionality as Strapi approaches the final v5.0.0 release.

Security Updates

No security fixes were mentioned in this release candidate. The changes were focused on functionality improvements and bug fixes rather than security vulnerabilities.

Performance Improvements

No specific performance improvements were highlighted in this release. The focus was primarily on bug fixes and UI enhancements rather than performance optimizations.

Impact Summary

This release candidate primarily focuses on bug fixes and quality-of-life improvements for both developers and content editors. The changes address several UI issues, particularly around date/time handling and sorting of complex data types, which should result in a more consistent and reliable admin interface experience.

For developers, the fixes to JavaScript templates and Vite configuration examples will improve the development workflow when creating new Strapi projects or plugins. The standardization of property naming (using documentId instead of id) contributes to a more consistent API.

While there are no major new features or breaking changes in this release, the cumulative effect of these bug fixes represents an important step toward stabilizing Strapi v5.0.0 as it approaches its final release. Users who have encountered issues with date formatting, locale handling, or template configurations will particularly benefit from this update.

Full Release Notes