Strapi Release: 4.14.0

TL;DR

Strapi v4.14.0: Enhanced Content Management with Stage Permissions and New Blocks Editor

Strapi v4.14.0 introduces two major features: granular stage permissions for review workflows and a new Blocks rich text editor (alpha). The update also includes TypeScript improvements with plugin types support, performance optimizations with React Query integration, and several bug fixes for Windows paths and attribute types. This release significantly enhances content management capabilities while improving developer experience through better typing and performance.

Highlight of the Release

• Stage permissions for review workflows allowing granular control over who can transition content between stages
• New Blocks rich text editor (alpha) providing enhanced content editing capabilities
• Improved TypeScript support with plugin types
• Performance optimization with React Query for InputUIDs data fetching
• Bug fixes for Windows paths and attribute types

Migration Guide

for v4.14.0

For the Blocks Editor (Alpha)

If you want to use the new Blocks editor:

1. Update your Strapi instance to v4.14.0
2. Create a new content type or edit an existing one
3. Add a new field with the type "Blocks" (available in the Rich Text section)
4. Configure the field as needed
5. Save your content type

Note that the Blocks editor is in alpha status and may undergo changes in future releases.

For Stage Permissions

If you're using Review Workflows:

1. Update your Strapi instance to v4.14.0
2. Navigate to Settings > Review Workflows
3. Configure your workflows and stages as before
4. You'll now see additional permission options for stage transitions
5. Configure which roles can transition content between specific stages

TypeScript Changes

If you're developing plugins or extensions using TypeScript:

1. Update your dependencies to use the latest Strapi packages
2. Take advantage of the new plugin types available in @strapi/types
3. Review any custom code that interacts with the content-manager or review workflows to ensure compatibility with the new typing system

Upgrade Recommendations

Recommendation: Standard upgrade recommended for all users.

This release introduces valuable new features and improvements without breaking changes, making it a recommended upgrade for all Strapi users. The new stage permissions feature is particularly valuable for teams using review workflows, while the Blocks editor (alpha) provides a preview of upcoming content editing capabilities.

How to upgrade:

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

After upgrading, run your migrations:

npm run strapi migrate
# or
yarn strapi migrate

Then restart your Strapi application.

Note: While the Blocks editor is marked as alpha, it's stable enough for testing but may not be recommended for production use cases where you need guaranteed stability.

Bug Fixes

• Windows Path Handling: Fixed an issue where Windows paths were not properly handled in plugins.js, causing problems for Windows users during development.

• Custom Field Server Options: Reverted a change to the plugin property on CustomFieldServerOptions that was causing compatibility issues.

• Namespace Mapping: Added the new blocks type to the namespace mapper to ensure proper handling of the new attribute type.

• TypeScript Definitions: Added missing TypeScript definitions for the new blocks attribute type, including:

  • Adding Attribute.Blocks to Attribute.Any
  • Adding 'blocks' to the Model's attributes
  • Fixing shared types resolving for Common.Schemas

• Radix Toolbar Dependency: Restored a missing dependency for the Radix toolbar component used in the Blocks editor.

New Features

Stage Permissions for Review Workflows

Strapi now offers granular permission control for content workflow stages. This feature allows administrators to define which users or roles can transition content between specific stages in the review workflow. Key capabilities include:

• Permission-based stage transitions
• Ability to filter available stages based on user permissions
• Support for partial updates of stage permissions
• Integration with the existing RBAC system

Blocks Rich Text Editor (Alpha)

A new rich text editor has been introduced in alpha status, offering a blocks-based approach to content creation:

• Modern block-based editing experience
• New blocks attribute type for content types
• TypeScript support for the new attribute type
• Integration with the existing content management system

This feature is marked as alpha and will continue to evolve in future releases.

Security Updates

No specific security fixes were mentioned in this release.

Performance Improvements

• React Query Integration: The InputUIDs data-fetching in the Content Manager has been refactored to use React Query, which provides:

  • Better caching of fetched data
  • Automatic background refetching
  • Improved loading states
  • Reduced unnecessary re-renders

• TypeScript Optimizations: The migration to TypeScript for various parts of the codebase improves type checking at build time, potentially reducing runtime errors and improving overall application stability.

Impact Summary

Strapi v4.14.0 delivers significant enhancements to content management workflows with two major features: granular stage permissions for review workflows and a new Blocks rich text editor (alpha).

The stage permissions feature transforms how teams can manage content approval processes by allowing administrators to define precisely which users or roles can transition content between specific stages. This enables more sophisticated editorial workflows with proper access controls.

The new Blocks rich text editor, while still in alpha, represents a major step forward in Strapi's content editing capabilities, offering a modern block-based approach similar to popular editors like Notion or WordPress Gutenberg.

Developer experience also sees improvements with enhanced TypeScript support, particularly for plugin development, and performance optimizations through React Query integration. These changes contribute to better code quality, fewer runtime errors, and improved application responsiveness.

The release maintains backward compatibility while adding substantial new functionality, making it a valuable upgrade for teams looking to enhance their content management processes and developer workflows.

Full Release Notes