TL;DR
Strapi v4.21.0 introduces significant enhancements to the Content Releases feature, making it stable for production use across multiple Strapi instances. The release also adds native Keycloak authentication provider support and fixes critical cache issues. These improvements focus on enterprise-level content management workflows and enhanced authentication options.
Highlight of the Release
- Content Releases feature is now stable and production-ready
- Support for scheduling content across multiple Strapi instances
- Native Keycloak authentication provider integration
- New API endpoint for creating multiple release actions at once
- Fixed cache issues in Content Releases
Upgrade Recommendations
This upgrade is recommended for all Strapi users, especially for:
- Users who need content scheduling capabilities in production environments
- Organizations running Strapi in multi-instance deployments
- Teams using or planning to use Keycloak for authentication
- Projects requiring efficient handling of bulk content release actions
The release contains important feature stabilizations and performance improvements with minimal risk of breaking changes. Follow the standard update procedure to upgrade from previous versions.
Bug Fixes
Cache Issues in Content Releases
Fixed cache-related issues in the Content Releases feature that could cause inconsistencies when working with scheduled content.
SQLite Locks
Resolved issues with locks when using SQLite as the database for Strapi, improving reliability for development environments.
New Features
Content Releases Stable Release
The Content Releases feature has graduated from experimental to stable status, making it production-ready. This feature allows content managers to schedule and publish content updates at specific times.
Multi-instance Content Scheduling
Content scheduling now works reliably across multiple Strapi instances, making it suitable for enterprise deployments with load balancing or high-availability setups.
Keycloak Authentication Provider
A native Keycloak authentication provider has been added to the users-permissions plugin, allowing seamless integration with Keycloak identity management systems without requiring custom code.
Bulk Release Actions API
A new API endpoint has been introduced for creating multiple release actions in a single request, improving performance and efficiency when working with content releases that involve many content items.
Security Updates
No specific security fixes were included in this release.
Performance Improvements
Bulk Creation of Release Actions
The new API endpoint for creating multiple release actions in a single request significantly improves performance when working with large content releases, reducing the number of API calls needed.
Improved Cache Handling
The fixes to cache issues in Content Releases improve the performance and reliability of content scheduling and publishing operations.
Impact Summary
Strapi v4.21.0 marks an important milestone with the Content Releases feature becoming stable and production-ready. This enables more reliable content scheduling workflows, especially in enterprise environments with multiple Strapi instances.
The addition of native Keycloak authentication support enhances Strapi's enterprise readiness by integrating with a popular identity management solution. This allows organizations to leverage their existing Keycloak infrastructure for Strapi authentication without custom code.
Performance improvements for content releases, particularly the new bulk API endpoint for creating multiple release actions, will benefit content teams working with large volumes of content. The fixed cache issues ensure more reliable operation of the content scheduling system.
Overall, this release strengthens Strapi's position as an enterprise-ready CMS with improved content workflow capabilities and authentication options.
Full Release Notes
💅 Enhancement
- [plugin:users-permissions] EE feat: Add keycloak native users-permissions provider (#19741) @derrickmehaffy
🚀 New feature
- [core:content-releases] removing scheduling future flag for stable release (#19754) @Feranchz
- [core:content-releases] fix content releases cache issue (#19791) @Feranchz
- [core:content-releases] new create many release actions endpoint (#19778) @Feranchz
📚 Update and Migration Guides
- General update guide can be found here
- Migration guides can be found here