Skip to content

v1.7.0 — related posts and experimental Payload 4 support

Choose a tag to compare

View all tags
@Ducksss Ducksss released this 10 Oct 03:48
v1.7.0
6e12a67
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Payload Components 1.7.0 adds the related-posts article component and experimental support for Payload 4.

New component

  • Related Posts (related-posts): a file-only article component for the end of a post template.
    • You pass the posts. It picks nothing itself, so manual picks and your own queries both work.
    • It always leaves out the post it's placed on, skips unsafe links and duplicates, and renders nothing when the list ends up empty.
    • Install it with npx payload-components add related-posts. See the docs.

Experimental Payload 4 support

  • Projects on Payload 4 prereleases are now detected and accepted. Every component installs, typechecks, builds and renders on the Payload 4 canary, and a nightly smoke test checks it against the current canary.
  • Peer ranges accept Payload 4 prereleases (^3.0.0 || ^4.0.0-0).
  • An unsupported Payload or Next.js major now gets an error that names the version, instead of a generic "unsupported project shape".
  • The starter base's Pages collection now restricts version reads to signed-in users, because Payload 4 makes published versions public by default. Payload 3 behaves the same as before.

Payload 4 itself requires Node 24.15+ and Next.js 16. Treat this support as experimental until Payload 4 is stable.

Upgrading

npx payload-components … picks up 1.7.0 automatically. If you pin the CLI, update it to 1.7.0. Existing component installs need no changes. If you scaffolded the starter base, payload-components diff shows the Pages access change, and update applies it.

Runtime dependencies are unchanged. MIT and community-first.

Verified publication

Published from production commit 6e12a67a5bc01a3c793c72876a37ad019d0f68ce. npm latest is 1.7.0, recorded with that exact git commit and a provenance attestation, and the @ducksss GitHub Packages mirror has 1.7.0 too.

  • Publishing workflow: the full release gate, packed-artifact checks, npm publication and the GitHub Packages mirror all passed on the first attempt.
  • Published-package check: npx payload-components@1.7.0 --help lists related-posts among its components; 1.6.1 did not.
Assets 2
Loading