Breaking change
Strapi: Breaking change: A vulnerability was patched in this release, with detailed disclosure delayed to allow use
What changed
- A vulnerability was patched in this release, with detailed disclosure delayed to allow users time to upgrade.
- Filtering a boolean field by an empty value now returns a 400 error.
- TRUE / FALSE and T / F are now read case-insensitively.
- Date-time filters in the Content Manager list view and audit logs now accept a date alone, matching the whole day.
- Email validation no longer slows down sharply on crafted input.
- The stricter email pattern rejects a dot inside a domain label.
- The upload Content API now passes only supported query parameters, in effect since 5.61.1.
- strapi export, import and transfer now apply --throttle and global transforms to every stage.
- Five keys are now required on the Upload File type in TypeScript.
- Core.PolicyHandler can now return a promise, and policyContext.state is typed.
- Sanitizer and traversal utilities from @strapi/utils now take and return objects with unknown values.
- A new feature shows an upgrade banner when Strapi is out of date.
- A new feature confirms before closing a modal with unsaved changes.
- Partial releases are a new feature.
Who it affects
- Projects with api.rest.strictParams enabled get a 400 for unknown upload parameters.
- TypeScript code that builds a File object itself, such as a test stub or mock provider, must set the now-required keys.
- TypeScript code that uses a policy handler's result directly must await it.
- Plugins using the admin Filters component with a date-time option are affected.
- Those running a transfer inside Jest must start Node with --experimental-vm-modules.
What to do now
- Pass filters through toApiFilters(filters, options) before calling the API when using the admin Filters component with a date-time option.
- Set the five required File type keys, for example to null.
- Check a field's type before using it.
- In strict-mode projects, type the entity parameter of a custom sanitizer or validator as Record.
Your users need to hear about your changes too
FoxPlug writes the changelog entry, the heads-up email draft and the social posts from what you ship.
Try it on your projectYour changelog, written for you
FoxPlug writes your changelog from your releases and commits in plain English and publishes it as a page and a feed your users can follow. The page above shows what that looks like for a product people really use.
Write my changelog See the changelog FoxPlug wrote from its own commits
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Written from your releases and commits, in plain English your users read
- Connect GitHub and new releases become new entries