Strapi Release: 4.0.0-beta.8

TL;DR

Strapi v4.0.0-beta.8 brings significant UI improvements across multiple areas, adds Node 16 support, enables API token authentication, and fixes several critical issues. This release focuses on enhancing the user experience with better navigation, improved content management interfaces, and more intuitive settings views.

Highlight of the Release

• Node 16 and NPM 7/8 support for project generation
• Migrated edit settings view with improved navigation and UI
• API token authentication strategy enabled
• Enhanced content management interface with required field indicators
• Fixed security configuration to allow GraphQL and documentation playgrounds

Migration Guide

No significant migration steps are required for this beta release. However, developers should note:

1. If you're starting a new project, you can now use Node 16 and NPM 7/8
2. If you were experiencing issues with GraphQL or documentation playgrounds, these should now be accessible with the updated security configuration
3. If you were using PostGIS extensions with PostgreSQL, tables from these extensions will now be properly ignored

Upgrade Recommendations

As this is a beta release (v4.0.0-beta.8), it's recommended for:

• Developers actively testing Strapi v4
• Teams preparing for migration to v4 from v3
• New projects that want to leverage the latest features

This release contains significant UI improvements and bug fixes that enhance the overall experience. If you're already using a v4 beta, upgrading to beta.8 is recommended to benefit from these improvements.

Production environments should continue using stable v3 releases until the final v4.0.0 release.

Bug Fixes

UI and Navigation Fixes

• Fixed keyboard navigation issues in various interfaces
• Fixed modal padding and border radius inconsistencies
• Fixed searchbar width and search functionality (prevented search from closing after typing)
• Fixed filter button spacing and alignment
• Fixed icon alignment issues throughout the application
• Fixed overflow bug with accordions in Content Manager

Functionality Fixes

• Fixed UI interactions for API token management
• Fixed copy/paste notification for API tokens
• Fixed magic link functionality with SSO
• Added explicit error messages when creating a user with existing email
• Fixed PostGIS tables handling by ignoring common extension tables

New Features

Content Management Improvements

• Added publish button in content creation view for streamlined workflow
• Added required field indicators in content manager edit view
• Improved dynamic zone components with better drag and drop functionality
• Enhanced accordion components for better content organization

Settings and Administration

• Migrated edit settings view with improved navigation and UI
• Added combobox interface to i18n settings for better language selection
• Enabled API token authentication strategy

Developer Experience

• Added support for Node 16 and NPM 7/8 in project generation
• Updated security configuration to allow GraphQL and documentation playgrounds

Security Updates

Security Configuration

• Updated security configuration to allow GraphQL and documentation playgrounds while maintaining appropriate protection
• Improved API token authentication strategy implementation

Performance Improvements

UI Performance

• Upgraded Design System multiple times throughout this release for better performance and consistency
• Improved component rendering in dynamic zones
• Optimized accordion group components to handle styling more efficiently

Impact Summary

This beta release significantly improves the user experience across Strapi's admin panel with numerous UI enhancements and bug fixes. Content editors will benefit from a more intuitive interface with better navigation, required field indicators, and improved dynamic zones. Developers gain Node 16 support and better API token management. The release also addresses several UI inconsistencies and fixes critical functionality issues.

The changes are primarily focused on refinement rather than introducing breaking changes, making this a solid iterative improvement in the v4 beta series. The addition of Node 16 support is particularly important for developers wanting to use more modern Node.js environments.

Full Release Notes