What’s New in Strapi 5 RC

The Strapi 5 Release Candidate (RC) is here, and we’ve made significant progress to ensure it’s ready for your projects. All breaking changes are done, meaning you won't encounter any disruptive updates from here to the stable release. We've defined the functional scope clearly, so what you see now is what you'll get in the stable version. Most critical bugs have been fixed, ensuring a more stable and reliable experience. The core features have undergone thorough quality assurance, so you can confidently explore them.

During the time between the RC and the stable release, we'll now be focusing on fixing medium and low-severity issues. This phase is all about polishing and refining the product based on your feedback and our ongoing testing. Our goal is to make sure that by the time the stable release rolls out, Strapi 5 will be robust, reliable, and ready for any challenge you throw at it.

So in short:

• ✅ Breaking Changes – Done. All the breaking changes have been implemented and thoroughly tested. You can start exploring the new version without worrying about unexpected disruptions.

• ✅ Critical Bugs – Squashed. We’ve tackled the critical bugs, making the RC stable enough for you to start testing more seriously. While we continue to iron out medium and low-priority issues, the core functionality is rock solid!

Key Features in Strapi 5 RC

• Draft & Publish: Manage your content seamlessly with our Draft & Publish system.
• Content History: Track changes and revert to previous versions of your content.
• TypeScript: Almost the entire codebase is now migrated to TypeScript, enhancing code quality and developer experience.
• Core Features: Enjoy robust features like Webhooks, API Token, RBAC (Role-Based Access Control), and DEITS (Data Import Export Transfer System).
• Plugin CLI: Easily extend Strapi with our new Plugin CLI.
• API Format: Improved REST and GraphQL API formatting for better performance and usability.
• Vite: Faster builds with Vite.

What’s the Difference Between the Beta and the RC?

The main difference is stability. In the RC, there are no more breaking changes, and we've fixed critical bugs. You can now start testing Strapi 5 for more serious purposes.

Who Should Use the Strapi 5 RC?

If you're eager to get a head start on migrating to Strapi 5, now is a great time to try it out locally. While we don't recommend starting production projects just yet, testing the migration in a local environment will help you get prepared and give you a sneak peek at the new features. It's an adventurous experience that will also provide invaluable feedback, helping us improve the final migration process for everyone. Your input will make a big difference in ensuring a smooth transition for all Strapi users.

• Prospective Users: If you're starting a proof of concept (PoC) or a new project, Strapi 5 RC is perfect for you.
• Explorers: Those curious about the new features and changes in Strapi 5, this is your chance to dive in.
• Plugin Developers: Now is a great time to upgrade your v4 plugins to Strapi 5.

Who Should Not Use the Strapi 5 RC?

• Existing Customers: If you're currently using Strapi 4 in a production environment, hold off on upgrading until the stable release.
• Production Projects: The RC is not recommended for production use. Stick with the stable version for mission-critical applications.

How to Get Started

You can install Strapi 5 RC using the following command:

npx create-strapi-app@rc <project_name>

What’s Next?

From now until the stable release, we’ll be focusing on fixing medium and low-priority issues. This period is crucial for us to gather feedback from you and ensure that the stable release meets your needs.

Join the Conversation

We’re eager to hear your thoughts and experiences with Strapi 5 RC. Join our community forum and share your feedback. Your input is invaluable as we move towards the final release.

Thank you for being part of the Strapi community. We’re excited to see what you build with Strapi 5!

Happy coding!