Home

>

Tools

>

Strapi

>

Releases

>

5.0.0-beta.5

Strapi Release: 5.0.0-beta.5

Pre Release

Tag Name: v5.0.0-beta.5

Release Date: 4/24/2024

Strapi LogoStrapi

Open-source headless CMS built with Node.js. Provides developers with complete freedom in choosing their favorite tools and frameworks for frontend development.

TL;DR

Strapi v5.0.0-beta.5 introduces significant enhancements to the History feature, including version restoration capabilities with confirmation modals and improved design. This release also includes important migration utilities for document published entries from v4, refactors the main navigation, reserves keywords for future Strapi 5 features, and fixes several bugs related to password handling, SSO frontend tests, and RBAC role management. The release represents continued progress toward a stable Strapi 5 with improved developer experience and user interface refinements.

Highlight of the Release

    • Complete implementation of the History feature with version restoration capabilities
    • Migration utilities for document published entries from Strapi v4
    • Reserved keywords for upcoming Strapi 5 features
    • Main navigation UI refactoring
    • Improved password handling in Users & Permissions service

Migration Guide

Reserved Keywords for Strapi 5

This beta introduces reserved keywords needed for upcoming Strapi 5 features. Developers should be aware that the following field names are now reserved and should not be used in content types:

  • documentId
  • documentScope
  • version
  • versions
  • history

If you're using any of these field names in your content types, you'll need to rename them to avoid conflicts with Strapi 5 features.

Migrating from v4

When migrating document published entries from Strapi v4, use the new migration utilities provided in this release. The migration process will:

  1. Handle document IDs appropriately
  2. Manage draft creation
  3. Properly discard drafts when needed

Note that tables that don't exist will be automatically ignored during the migration process.

Upgrade Recommendations

For Beta Testers

If you're already testing Strapi v5 beta releases, we recommend upgrading to v5.0.0-beta.5 to take advantage of the new History feature and other improvements. This release represents significant progress toward a stable Strapi 5 release.

For Production Users

This is still a beta release and not recommended for production environments. Continue using Strapi v4 for production applications while monitoring the progress of v5 beta releases.

Upgrade Steps

  1. Update your package.json to reference strapi: "5.0.0-beta.5"
  2. Run yarn install or npm install to update dependencies
  3. Be aware of the newly reserved keywords and ensure your content types don't use these field names
  4. If migrating from v4, use the new document migration utilities

Bug Fixes

User Interface Fixes

  • Fixed double modal toggle when deleting RBAC roles
  • Improved history design details for better user experience
  • Added render prop to use VersionInputRenderer for more flexibility

Authentication and Security Fixes

  • Fixed SSO frontend tests
  • Improved password handling in the Users & Permissions service to ensure passwords are properly hashed

Data Handling Fixes

  • Sanitized history versions data field to prevent potential issues
  • Fixed TypeScript errors related to naming

New Features

History Feature Fully Implemented

The History feature has been fully implemented in this beta release, allowing users to:

  • Restore previous versions of content with a new restoration flow
  • View version history with improved UI design
  • Receive confirmation prompts when restoring versions to prevent accidental changes

Migration Utilities for v4 Documents

New migration utilities have been added to help with the transition from Strapi v4:

  • Support for migrating document published entries from v4
  • Dynamic registration of internal migrations
  • Improved transaction utilities for testing

Main Navigation Refactoring

The main navigation has been refactored with:

  • New NavBrand component replacing the Design System component
  • Improved logo handling and presentation
  • Better padding and layout adjustments

Security Updates

Password Handling

  • Fixed an issue in the Users & Permissions service where passwords weren't being properly hashed, ensuring better security practices for user credentials

Data Sanitization

  • Improved sanitization of history versions data field to prevent potential security issues when handling version data

Performance Improvements

Test Utilities Improvements

  • Refactored test utilities in transaction util for better performance and reliability
  • Added API tests for the History feature to ensure stability

Dependency Management

  • Removed js-cookie dependency to reduce bundle size and simplify the codebase

Impact Summary

Strapi v5.0.0-beta.5 delivers significant improvements to the content management experience with the full implementation of the History feature, allowing content editors to restore previous versions with confirmation safeguards. Developers will benefit from enhanced migration utilities for transitioning from v4, particularly for document published entries, and should note the newly reserved keywords for upcoming Strapi 5 features.

The release also addresses several important bugs, including fixes for password handling in the Users & Permissions service, improvements to the RBAC role deletion flow, and better SSO frontend test reliability. UI enhancements include a refactored main navigation with improved logo handling and better history design details.

This beta release represents continued progress toward a stable Strapi 5, with a focus on improving both the developer experience and end-user interface. While still not recommended for production use, it provides a good preview of the features and improvements coming in the final release.

Full Release Notes

What's Changed

Full Changelog: v5.0.0-beta.4...v5.0.0-beta.5

Statistics:

File Changed141
Line Additions5,835
Line Deletions1,990
Line Changes7,825
Total Commits30

User Affected:

  • Can now restore previous versions of content with the new History feature
  • Benefit from improved UI design for the History feature
  • Will see confirmation modals when restoring content versions

Contributors:

christiancp100markkaylorremidejinnerdvationsMarc-RoigConvlyMattieBeltsimotae14alexandrebodin