September gave you a new Media Library and folders for your content types. October and early November took that work to the places you use every day. From v5.57 to v5.62, you can rename a field and keep its data, the new Media Library is inside every entry, and large entries open, save and publish much faster. Outside the releases, Strapi AI Enterprise brings Strapi AI to self-hosted Enterprise projects, and the Community Hub now has accounts and a Partner Portal.
One important thing to know before you read on: Strapi now needs Node.js 22. The details are in "Before you upgrade".
Rename a field and keep its data
You can now rename a field without losing what is stored in it (v5.57.0, #26749). Until now, a rename in the Content-Type Builder was a delete and a create. The old column was dropped, and its data went with it. Most teams learned to never rename anything, so production schemas kept field names that nobody wanted. Now Strapi asks you to confirm the rename before you save, then writes a migration file. The migration runs on every environment before the schema sync, so local, staging and production all keep their data.
Three things to know:
- It covers fields only for now. A rename of a component, a dynamic zone or a content type still loses its data.
- The migration file is part of your code. Commit it and ship it with the schema change.
- The name of a field is also its name in the API. After a rename, update the frontends and apps that read that field.
The rest of the admin follows the new name. Conditional fields that point at a renamed field keep working (v5.58.0, #27953), and your list view keeps its columns (v5.59.0, #28036). There is also a strapi rename:field command if you prefer the CLI (docs).
This was one of the most requested changes on the feedback board. Thanks to everyone who voted for it.
The new Media Library is now inside your entries
In September the Media Library page was rebuilt: a folder tree in the sidebar, uploads that run in the background, one list with search, sort and filters, and a details panel with crop and focal point. The previous roundup has the details. But the place where editors attach files most often, the media field inside an entry, still used the old screens. That is now fixed, release by release.
The media field shows all its files at once (v5.59.0, #27848). The old field showed one file at a time in a carousel, with arrows to see the others. Uploads opened a wizard that covered the form and asked you to confirm. Now the field is a list, one row per file. Drop files on it and the upload starts immediately, with the progress in a corner of the screen. You can continue to edit the entry while it runs.
One "Add asset" menu for every way to add a file (v5.59.0, #27856). Browse the library, upload from your device, or upload from a URL. Upload from a URL is new in the field.
The picker is the full Media Library (v5.60.0, #28091). "Browse library" opens the same folders, search and filters as the Media Library page. A "Selected assets" tab lets you reorder your selection by drag and drop, and files of the wrong type are greyed out, so you cannot pick a PDF for an image field.
Rich text uses the same picker, and you can drop images into Blocks (v5.61.0, #28176). The image button in the Markdown and Blocks editors opened the old dialog, so one library had two different pickers. Both editors now open the new one. In the Blocks editor, you can also drag images from your computer straight into the text. They upload and land where you dropped them.
Edit a file without leaving the entry (v5.61.0, #28283). The pencil on a media field opens the full asset details, where you can replace, crop or delete the file.
Rotate images, and right-click for actions (v5.57.0, #27714, #27816). The image editor has a rotate button next to crop and focal point. A right click on an asset or a folder opens its actions menu.
AVIF images get their dimensions and responsive formats (v5.61.0, #28170). They were stored without them before.
All of this follows the same switch as the Media Library page. If you set useLegacyMediaLibrary: true, you keep the old field and the old picker.
Large entries open, save and publish faster
If your content types have many relations and components, this is the section for you.
Publishing an entry that many components link to no longer takes minutes (v5.59.0, #27942). Think of a link or button component used in the dynamic zones of thirty content types. To publish one target entry, Strapi checked every component instance against every possible parent, one query at a time. In the team's test, one publish ran 266,612 queries. It now runs 83. On PostgreSQL, the same publish went from 144 seconds to about 150 milliseconds. This one started from a customer ticket.
A save writes only what changed (v5.60.0, #28092). The admin sends the whole entry on each save, and Strapi wrote every component again, changed or not. Now it compares first. On a test entry with 90 components, a save with no changes went from 360 database statements to 34, and a publish from 1,496 to 632. Strapi also stops building webhook data after each save when no webhook is there to receive it.
The edit view loads what you look at (v5.61.0). Rows of a long entry now appear progressively, and relation fields fetch their data only when they are near the visible part of the page.
Webhooks that send only what you need
You can now choose webhook events per content type (v5.60.0, #27931). A webhook used to fire for every entry of every content type, and your receiving service had to filter out what it did not need. In Settings > Webhooks, the events table now lists your content types under the Entry row. You can check Create on articles and Publish on pages in the same webhook. Events checked on the Entry row are still sent for all content types, so your existing webhooks do not change.
One webhook request per release, not one per entry (v5.61.0, #27909). When a webhook listens to entry publishes and to release publishes, a release with ten entries sends eleven requests: one for each entry and one for the release. If that webhook starts a build of your site, that is eleven builds. Set webhooks: { deduplicateReleaseWebhooks: true } in config/server, and that webhook gets one request for the release. Webhooks that listen to entries only do not change, and an entry published outside a release still sends its own request. The setting is off by default.
Strapi AI Enterprise
Strapi AI is now available on the Enterprise plan, and it runs on your own AI provider. Until now, Strapi AI ran only on the managed AI service of Strapi, on the Growth plan, so Enterprise teams could not use it. Strapi AI Enterprise runs on the AI provider your security team already approved. Your content goes straight to it and never passes through Strapi.
It covers AI translation and AI media metadata, with unlimited usage and no credits. It is a paid add-on on the Enterprise plan, for self-hosted projects on Strapi v5.59.0 or later. The Enterprise updates post shows how it works and how to set it up, and the documentation has the list of tested AI providers.
Audit logs record more
Audit logs answer one question: who changed what, and when. In this window they started to record Review Workflow actions (v5.57.0), failed admin logins and the accounts that SSO creates (v5.58.0), changes to the SSO settings (v5.60.0), and Content History restores, discarded drafts, settings changes and every media action (v5.61.0). The date filter now works by day (v5.62.0): a date gives you the logs of that day, not of one exact instant.
Audit logs changed in almost every release since September, and you can now export them as a CSV file. The Enterprise updates post has the full picture, and the documentation has the full list of events.
Billing and licences
You can see what your licence includes, inside Strapi (v5.58.0, #27034). Settings > Overview now shows your plan, seats, licence status, renewal date and what the licence covers. Before, the only way to find out was to ask.
The Billing Portal has a new version. At billing.strapi.io, customers with several billing accounts now land straight in the portal and filter by account on every tab. Subscriptions can be grouped by status, plan or account. The documentation covers it.
Enterprise plugins install with one command (v5.57.0, #27849). strapi enterprise install sets up the private registry, finds the version that matches your Strapi, and prints the configuration to add. This is how you install the AI Enterprise plugin. From v5.62.0, the command also shows which plugins your licence does not include.
Content Manager and admin panel
Discard changes now warns you about relations it will remove (v5.57.0, #27815). Discard takes the draft back to the published version, and the published version never holds relations to draft entries. So those relations were removed with no message. The dialog now tells you how many linked entries are still drafts before you confirm.
A release can publish what is ready and skip the rest (v5.62.0, #28339). Until now, one entry that could not be published stopped the whole release. You can now set a release to allow partial publishing. It publishes the entries that are ready, skips the others, tells you why for each one, and lets you create a new release from the skipped entries. The default is still all or nothing.
Copy an existing component (v5.62.0, #26611). In an entry, you can now copy a component that is already filled in, and you do not have to fill a new one from zero.
A warning before you edit a shared field in another locale (v5.62.0, #27370). A field that is not localized has one value for all locales. Strapi now warns you before you change it from a secondary locale.
No more lost edits in a modal (v5.62.0, #28239). Strapi asks you to confirm before it closes a modal that has changes you did not save.
A banner tells you when your Strapi is out of date (v5.62.0).
Login works again with a custom admin URL (v5.59.0, #27619). Since v5.51.0, a project with admin.url set to something like /dashboard could not log in, and the documented workaround ended the session after 30 minutes. Strapi now gives each admin cookie the correct path by itself. You can remove the auth.cookie.path workaround.
Filter on "false" in the list view (v5.59.0, #27938). A filter on a boolean field set to false was ignored. Unset boolean fields also show as neither true nor false now (v5.58.0, #28014).
Custom RBAC conditions in a custom category are kept (v5.59.0, #28020). They were discarded on save before.
Database
A connection function no longer holds a pool connection forever (v5.59.0, #27979). If you pass your database connection as a function on PostgreSQL or MySQL, Strapi took one connection from the pool at startup and never gave it back. With a small pool, that was 20 to 50% of your capacity, and "Timeout acquiring a connection" errors were more likely.
Moving a relation to the start of a list works on MySQL and MariaDB (v5.61.0, #28289).
Developer tools
The strapi CLI no longer loads the admin build tools on every command (v5.57.0, #27910). Commands that do not build the admin panel start with less to load.
The Documentation plugin no longer runs out of memory on projects with many relations (v5.57.0, #27780).
The MCP server no longer builds the schemas of all tools on every request (v5.60.0, #28116).
Before you upgrade
Upgrade to v5.62.0 for a security fix. This release fixes a vulnerability. The details will come later, to give everyone time to upgrade first.
Node.js 22 is required. From v5.59.0, Strapi needs Node.js 22.19.0 or later, because of a dependency update (#27934). v5.61.0 removes Node 20 support completely (#26631). Check the Node version of your servers and your CI before you upgrade.
Custom database queries with limit on a delete behave differently (v5.59.0, #27982). If your code uses strapi.db.connection and calls delete() with limit or having, or truncate() with where, having or limit, it now throws on PostgreSQL and SQLite. MySQL now applies the limit. Before, the limit was ignored and every matching row was deleted. Check your plugins and scripts.
limitInputPixels must be a number or a boolean (v5.59.0, #27161). The upload plugin now applies sharp.limitInputPixels, and Strapi does not start if the value is a string. A value read from an environment variable is a string, so use env.int().
Token and role names stop at 255 characters (v5.59.0, #28004, #28002). This applies to the name and description of API tokens, admin tokens, transfer tokens and admin roles. Existing longer values keep working, but you must shorten them the next time you save.
Deleting an entry changes past releases (v5.59.0, #28023). When you delete an entry that was part of a published release, the entry is removed from that release and the release status can change from "done" to "empty" or "ready". The published content is not affected. From v5.62.0, a release that is already published is not changed any more (#28169).
strapi.query is deprecated (v5.60.0, #28139). It still works. Plan to move your custom code away from it.
Boolean filters reject values that are not valid (v5.62.0, #28172). A filter on a boolean field with a value such as an empty string, yes or 2 now returns a 400 error. Before, it usually matched true. Check the API calls of your frontends.
Date filters match the whole day (v5.62.0, #28367). In the list view, a date alone now matches that day. If your plugin uses the admin Filters component with a date and time option, pass its filters through the new toApiFilters helper.
The Community Hub: accounts, organizations and a Partner Portal
Not everything new is in a release. The Community Hub is the home of what the community builds for Strapi, and it is where the Marketplace now lives. You find more than 380 plugins, providers and tools there, with filters by type, category and integration. You also find templates such as Launchpad, guides to connect Strapi with frameworks like Next.js, Astro and Nuxt, showcases of projects built with Strapi, and the profiles of the partners and the people behind all of it.
New to the Hub? Take the full tour, from the first search to your own profile.
Two things changed there in this window.
You can now have an account
Until now, you submitted a plugin and then had to ask us for each change. Now you sign in and do it yourself. Sign up with an email and a password or with a magic link, and add two-factor authentication if you want it. Then build your profile with your picture, your bio and your GitHub link. Your packages show on it.
The main change is for maintainers. You can update the logo, the description and the readme of your plugin or template when you want. You can also create an organization and invite your colleagues, as admins who can make changes or as members who show on the profile page.
If you submitted a plugin before this change, you already have an account, and you got an email that explains how to get access to it. New submissions now need an account, so sign up first.
Partners have a Partner Portal
Strapi partners now manage their own partner profile on the Hub. And when they sign in, they get a Partner Portal: one place with what they need to sell and build with Strapi. It opens with sales enablement (how the program works, pricing and positioning), tech enablement (learning paths, architecture guides and demo licenses) and reusable content (the Strapi logo pack and the co-marketing program).
Do you maintain a plugin, a template or a starter that is not on the Hub yet? Submit it, so other Strapi builders can find it.
What's next
Field renames are the first step. Renaming components, dynamic zones and content types without losing data is on the public roadmap. There is no date yet.
Thank you
Thank you to everyone who opened an issue, reviewed a pull request or sent a fix in this window. Among the people named in the release notes: unrevised6419, cpruijsen, dijedontahiri, jasleenkaur-qed42, simpleqt, kwy404, theluckystrike, Mohith26, onyxdevs, aayushbaluni, sony9154, wakqasahmed, MrAi0, Ranbir5ingh, Na5co, mmurakaru, Adzouz, devCluna, DipanshuAmbilkar03, giu1io, jhoward1994, ricardofrancoli, valfur03 and butcherZ. See you in the next one!
Release notes
This post covers the changes most likely to matter in your day. For the full list, see the release notes:
