Repository navigation
Breaking: Payload 3 now needs 3.25.0 or newer
Blocks now set admin.group (see below). Payload added admin.group to its Block type in 3.25.0, so with 3.24 or older the TypeScript build fails with TS2353. Every manifest therefore declares payload as ^3.25.0 || ^4.0.0-0:
addrefuses a project whose Payload is older than 3.25.0.doctorwarns when the installed Payload is older than 3.25.0.
If your project is on Payload 3.0–3.24 (released November 2024 to February 2025), you have two options: upgrade Payload to 3.25 or newer, or keep using payload-components@1.8.0. Nothing else in the CLI's commands or flags changes. Payload 4 support is unchanged. (#654)
Blocks Drawer groups
- Every block is listed under its family heading. All 79 blocks set
admin.group, so Payload's "Add Layout" drawer groups them under the same headings the catalog uses: Hero, Feature, Pricing, Call to action, Testimonials, and so on. Before, an editor with a few dozen blocks installed scrolled one long flat list. (#654) - New components get a group too. The component template sets one, and
payload-components newcopies the group of the closest existing block. A new family gets its capitalized first word. (#654) - Existing installs. Each block manifest moves up one minor version. Run
payload-components updateto pick up the group. No stored Payload data changes. (#654)
Payload 4 (experimental)
doctorchecks the real minimums. On a Payload 4 project,doctornow warns below Next.js 16.4.0 and Node.js 24.22.1, the versions Payload 4 itself requires. 1.8.0 checked against 16.2.6 and 24.15.0. The component docs,/llms.txtand the README state the same minimums. (#647)- Tested every night on the newest Payload 4 build. The nightly smoke now follows Payload's prerelease line across dist-tags; it had been stuck on
4.0.0-canary.39. The full catalog installs, builds and renders on4.0.0-beta.7in CI. The main nightly stays on the newest stable Payload 3, so Payload 4 becominglatestwon't break it. (#647, #653)