On May 6, 2026, Strapi released version 5.45.0 with an extended CTB API for plugins, sorting by publication status and improved admin token support. For all Portalworks projects, this version is a milestone that at the same time sends an important signal: Strapi 4 is considered EOL (end of life) as of the end of April 2026.
The relevance of this development lies in a fundamental shift in requirements. For agency and clients, there is no longer a strategic pause – if you are still running on v4, you are in a transition period with limited backing. From April 2026, only limited updates to Strapi 4 can be expected, and after the EOL date, security patches will probably no longer be provided either.
Technical implications for projects:
The new features in v5.45.0 affect core functionality. The extended CTB API for plugins simplifies plugin development, and the admin token extension with admin permissions and user-owner functionality enables finer access control for automated backend processes. Official support for Strapi v4 ended in October 2025; from that point on, only critical updates and security patches will be provided until April 2026.
The key question for every running v4 project: A migration plan is now mandatory, not optional. Migrating to Strapi 5 secures continued support, access to new features and improved performance. However, the breaking changes are considerable – the biggest breaking change: the Entity Service API has been replaced by the Document Service API, and flat API responses replace the nested data.attributes wrappers.
Expert position and action:
Strapi v5 is not just a performance update. It is a paradigm shift in how Strapi thinks about content and APIs; the release focuses on consistency, performance and scalability. For existing v4 projects, this means: a migration audit is required now, not later.
Recommendation:
1. Immediately (May/June): Take inventory of all running v4 projects – check plugin compatibility, assess custom code
2. Phased migration: Strapi offers a retro-compatibility header that allows backend and frontend to be migrated independently and at their own pace
3. Testing buffer**: The migration should be completed before April 2026 is reached – that leaves a few weeks for any outstanding security patches
The technical reality is clear: v5 is the future. Within the agency, v5 should already be established as the standard for new projects, and existing v4 client projects need a concrete migration roadmap by Q1 2026.
Portalworks supports your Strapi implementation – from the v4-to-v5 migration to the optimization of DXP scenarios with extended plugin APIs. Contact us for a free migration assessment.
