Quality First: Our Commitment to a (Even) More Robust Strapi

v5.31.1: 24 bug fixes. v5.30.1: 12 bug fixes. v5.29.0: 20 stability improvements. The pattern is clear, quality is now our top priority until the end of the year and throughout 2026.

Why This Matters?

We shipped significant features in 2025, including TypeScript 5.0 support, Responsive Admin Panel, Conditional Fields, Live Preview, Homepage Customization, Database Transactions, Draft & Publish improvements, Strapi AI, Shopify/Cloudinary/BigCommerce integrations, and more. But velocity came at a cost to stability.

You've been clear through GitHub issues and community feedback. The top-voted requests aren't flashy new features; they're reliability fundamentals. Better error handling, performance optimization, data transfer, and media library stability. Support tickets echo the same patterns.

How did we get there?

We're a small team maintaining three products that serve different needs: Strapi Community Edition (open source), Strapi Enterprise Edition, and Strapi Cloud. Each one requires attention, resources, and care. As an open-source company, we face a constant balancing act: generating revenue to sustain the project while staying true to our commitment to the community that makes Strapi what it is.

It's not easy. When we prioritize one, the other can slip. And we know you've felt that in some ways, lingering bugs, features that would benefit from additional iterations, or pull requests that go unreviewed for some time.

What we are doing about it

Recent releases show the shift. v5.31, v5.30, and v5.29 merged over 70 PRs focused on quality.

Here is a summary of these updates across various parts of the codebase:

• Content Modeling: Fixed schema generation with negative numbers, resolved enum defaults, and Content-Type Builder accessibility.
• Content Manager:
  • Content Internationalization: Fixed field flickering on i18n rerenders, bulk unpublish with new locales, draft relation counts, locale picker ordering, publish/unpublish with locales.
  • Responsiveness: improved responsiveness of the left menu and subnav.
  • General Fixes: preserved hidden fields during form submission, admin panel safety (prevented accidental self-deletion), dynamic zone configurations, and bulk operations.
  • Media Library & Upload: Resolved modal click issues, file-type detection, folder selection, and enhanced asset selection with accessibility improvements.
• Developer Experience: Improved TypeScript errors, customized CORS settings in the GraphQL plugin, and Node 24 support added.

Quality isn't just our focus at the core; it extends to everything we do, from the documentation to the Marketplace and the LaunchPad demo application:

Here are the latest updates from the Marketplace:

• We have migrated numerous Strapi plugins from Strapi 4 to Strapi 5 i.e plugin-rest-cache,
• We've removed outdated v4 plugins, eliminated duplicate listings, and increased visibility for higher-quality plugins, while also adding visibility warnings for unmaintained packages.
• Stale plugins (no updates in 2+ years) are being deprecated. Moving forward, we plan to raise quality standards and work toward automated compatibility testing with each Strapi release.

We’ve also been busy reworking our documentation. To name a few recent improvements:

• We added a new section on How to create admin permissions from plugins.
• We developed the Information on aggregation in GraphQL API and GraphQL API related v5 migration.
• We reworked the Document Service API page to better explain documentId and available methods.
• We improved the Lifecycle functions reference with more explanations and examples.

We need your help

Here's the truth, though: We need your help. We're prioritizing quality and committing resources, but we can't do this alone. Community contributions such as detailed issues, PRs, and documentation updates make a massive difference.

For instance, last month's releases included 9 merged PRs from a diverse group of community contributors in countries like Colombia, India, Egypt, and Austria. Here are some of the amazing people who contributed:

• Ayush @Ayushd785
• Chaitya @chaitya-titan
• Daniel Garcia @dagadevelop
• Dmitry Maklygin @dmaklygin
• José Luis @SalahAdDin
• ndaemy @ndaemy
• Razim Saidov @razims
• Sam Phillemon @Sam-Phillemon9493

The unglamorous work matters most. In open source, it's the steady contributors who review PRs, triage issues, update docs, and fix bugs that build reliable software. We see you. We value you. Making contributions count requires effort from both sides. We're making a significant push to review PRs more frequently and merge them faster. The entire team is now pitching in to support this effort. On the contributor side, following the guidelines carefully makes a huge difference—writing clear descriptions, linking related issues, including tests, and providing all the necessary context helps us merge contributions quickly and efficiently.

Why should you contribute to Strapi?

Building on our promising Documentation Contribution Program, we plan to provide stronger recognition and clearer incentives to code contributors, including Strapi goodies from the Strapi Shop and more!

We're also planning to start allocating unused Open Collective funds directly toward contributions to the core codebase and popular plugins currently hosted under the Strapi Community GitHub Org: such as the plugin-rest-cache, strapi-plugin-sitemap, strapi-plugin-import-export-entries, strapi-plugin-seo, and strapi-plugin-menus!

We're still finalizing the details of this program, so please stay tuned for more information. In the meantime, we invite you to check out our GitHub repository and look for issues or PRs that could use some love!

Looking ahead to 2026

In summary, our plan is to prioritize the foundations that directly impact reliability and stability. We'll tackle as many of these topics as possible, with progress dependent on both our internal resources and community contributions.

Main focus areas currently include:

• Media Library performance and reliability
• Bulk operations reliability
• Relations handling
• Filters and search functionality
• Performance improvements include faster build times, optimized rendering, and more efficient compilation.

Every year, we ask the community to identify the issues that matter most to them. Join the discussion on GitHub and tell us what we should prioritize.

Your feedback and contributions directly shape our roadmap!