Skip to main content
This guide covers upgrading from 0.x to v1. v1 needs Payload 4.0.0-canary.38 and Next.js 16.4 or later.

0.x to v1

Some options were renamed in v1. The plugin throws at boot when it finds an old name, and the error names the new one.
Before (0.x)
After (v1)
Entity security now uses the same words as the security option. A true or false value throws at boot:
Before (0.x)
After (v1)
An extension transform now gets one object with doc and the build context. A transform with two parameters throws at boot. A transform that still treats its argument as the document fails the spec request, because it returns the object, not a document. Check every transform:
Before (0.x)
After (v1)
Some defaults changed too:
  • The spec no longer takes servers from the request Host header, because a client can fake it. It uses serverURL from your Payload config, or servers. To keep the old behavior for known hosts, list them in trustedHosts.
  • An extension transform that throws now fails the spec request. Before, the plugin logged the error and served the document without that transform.
  • The docs UI loads a pinned library version with Subresource Integrity.
  • Upload read schemas show variants instead of sizes, because Payload renamed image sizes to variants. See the Payload release notes.