Strapi Release: 4.0.0-beta.15

TL;DR

Strapi v4.0.0-beta.15 brings several important improvements and fixes to the CMS platform. This release focuses on enhancing the CLI experience, fixing SSO authentication issues, improving the WYSIWYG editor, and addressing various UI and functionality bugs. The update also includes Design System upgrades and makes the lastname field optional for users. These changes improve the developer experience and fix critical issues reported by the community.

Highlight of the Release

• Made lastname fields optional for user accounts
• Fixed SSO authentication for existing users
• Improved CLI with better path validation and warning messages
• Enhanced WYSIWYG editor with better placeholder styling
• Updated Design System to alpha v68
• Added usage tracking for API tokens
• Fixed relation fields to prevent connections to private content types

Migration Guide

No specific migration steps are required for this beta release. However, if you're using custom implementations that rely on the lastname field being required, you should update your code to handle cases where it might be empty or null.

Upgrade Recommendations

As this is a beta release (v4.0.0-beta.15), it's recommended for testing environments and early adopters who want to provide feedback on the upcoming v4 features. Production environments should continue using stable releases unless specifically testing v4 functionality.

To upgrade from v4.0.0-beta.14:

npm install [email protected]
# or
yarn add [email protected]

After upgrading, restart your Strapi application and check for any console warnings or errors that might require attention.

Bug Fixes

SSO Authentication

Fixed an issue with SSO authentication by implementing a custom findOneByEmail function to properly search for existing users.

WYSIWYG Editor

• Fixed placeholder styling and color in the WYSIWYG editor
• Applied consistent font styling for all CodeMirror instances
• Fixed Strikethrough import in WysiwygNav

Content Manager

• Fixed missing descriptions in Content Manager relation boxes
• Fixed useTrackRef in EditView
• Fixed validation issues in the Content Manager

Content-Type Builder

• Prevented relations to private content types (API token and locale)
• Fixed naming errors for files path

CLI

• Fixed frontend dependencies installation
• Fixed monorepo dependencies installation
• Fixed issues with package management in starters

New Features

Optional Lastname Fields

The lastname field is now optional for user accounts, making the user registration and management process more flexible.

API Token Usage Tracking

Added usage tracking capabilities for API tokens, allowing administrators to better monitor and manage token usage across the application.

CLI Improvements

• Added validation for installation paths before starting the CLI prompt
• Added warning messages when creating content-types without attributes
• Updated create-strapi-starter to use npm on v4 by default

Design System Updates

Updated to Design System alpha v68, bringing UI improvements and new components.

Security Updates

No significant security fixes were included in this release.

Performance Improvements

Watch Mode

Improved watch mode functionality with better description and error handling, enhancing the development experience.

Error Handling

Enhanced error logging with better color coding and more descriptive messages, making debugging more efficient.

Impact Summary

This beta release brings several quality-of-life improvements for developers and administrators using Strapi v4. The optional lastname field provides more flexibility in user management, while the SSO authentication fix resolves a critical issue for organizations using single sign-on.

CLI improvements enhance the developer experience with better validation and feedback, particularly when creating new projects or content types. The WYSIWYG editor enhancements improve the content editing experience with better placeholder styling.

The addition of API token usage tracking provides administrators with better insights into how their API is being used, which is valuable for monitoring and security purposes.

Overall, this release focuses on polishing the v4 experience ahead of its stable release, addressing community feedback and fixing reported issues.

Full Release Notes