useAsTitle
virtual fields linked with a relationship field (#11805) (1c99f46)createSchemaGenerator
(#12043) (71e3c78)where
querying by join fields (#12075) (466dcd7)relationTo
with overrideAccess: false
(#11999) (b9ffbc6)dbName
is used (#11995) (09782be)file
field is only serialized at top-level for upload-enabled collections (#12074) (112e081)_payload
& field explanation (#12025) (83319be)dev:generate-types
(#11994) (97e2e77)password
field when using disableLocalStrategy: true
(#11893) (8ad22eb)ValidationError
error message when label
is a function (#11904) (dc793d1)doc
input for scheduled publish job if it's enabled only for globals (#11892) (760cfad)deleteOne
fails when the where
query does not resolve to any document (#11632) (4ebd3ce)migrationTableExists
doesn't check in the current transaction (#11910) (f310c90)draft: true
when querying joins (#11869) (e5690fc)clientUploads.routerInputConfig
to the handler (#11962) (8e93ad8)modifiedOnly
default to true
(#11794) (21f7ba7)Query Presets allow you to save and share filters, columns, and sort orders for your collections. This is useful for reusing common or complex filtering patterns and column configurations across your team. Query Presets are defined on the fly by the users of your app, rather than being hard coded into the Payload Config.
https://github.com/user-attachments/assets/1fe1155e-ae78-4f59-9138-af352762a1d5
This release bumps the peer dependency version of Next.js to 15.2.3
to address a security vulnerability. Next.js Blog post here for more detail. (PR #11823).
NOTE: This vulnerability does not affect any of the functionality of Payload, as the framework does not leverage anything affected in the vulnerability. This would only affect you if you've built additional functionality on top of Payload using additional Next.js middleware.
draft: true
when querying docs for the join field (#11763) (1b2b6a1)This release upgrades the lexical dependency from 0.27.1
to 0.28.0
.
If you installed lexical manually, update it to 0.28.0
. Installing lexical manually is not recommended, as it may break between updates, and our re-exported versions should be used. See the yellow banner box for details.
If you still encounter richtext-lexical errors, do the following, in this order:
node_modules
pnpm-lock.json
)pnpm install
)forceSelect
collection / global config property (#11627) (5e3d07b)id
to create operation data without custom IDs (#11709) (f442d22)select
& radio
field option labels accept JSX elements (#11658) (3c92fbd)useAsTitle
(#11707) (ef527fe)useDocumentInfo
(#11686) (ff2df62)We’ve introduced a new opt-in flag that can cut Payload’s compile times in half during development. To enable it, add the following to your next.config.js:
const nextConfig = {
// ...
}
-export default withPayload(nextConfig)
+export default withPayload(nextConfig, { devBundleServerPackages: false })
In some rare cases, you may see unexpected behavior if your project relies on server-only Payload dependencies being bundled during development. Because of this, we’ve made the feature opt-in for existing projects.
This release upgrades the lexical dependency from 0.21.0
to 0.27.1
. Alongside table improvements and bug fixes, this version bump lays the groundwork for frequently requested features like color pickers.
If you installed lexical manually, update it to 0.27.1
. Installing lexical manually is not recommended, as it may break between updates, and our re-exported versions should be used. See the yellow banner box for details.
If you still encounter richtext-lexical errors, do the following, in this order:
node_modules
pnpm-lock.json
)pnpm install
)payload-locked-documents
collection (#11624) (8f3d1bd)updateVersion
read result (#11589) (e9afb36)i18n
configuration (#11590) (5d65cb0)payload migrate:create
flags (#11592) (3de1636)disablePayloadAccessControl: true
(#11530) (5cc0e74)clientUploads
is not set (#11527) (e36ab6a)indexes
default value sanitization (#11534) (f0ea918)