v3.0.0-beta.36

v3.0.0-beta.36 (2024-05-23)

Features

• next.js 15, react 19, react compiler support (#6429) (35f961f)
• add website template (#6470) (85bfca7)
• ui: split up Select component into Select and SelectInput (#6471) (661a4a0)
• richtext-lexical: various UX and performance improvements (#6467) (78579ed)
• richtext-lexical: improve block dragging UX (6b45cf3)
• next: server-side theme detection (#6452) (1fe9790)
• translations: add Hebrew translation (#6428) (3c0853a)
• richtext-lexical: various gutter, error states & add/drag handle improvements (#6448) (6c95287)

Bug Fixes

• adds host to initPage req creation (#6476) (72c0534)
• isHotkey webpack error (#6466) (73d0b20)
• richtext-lexical: order of add/drag handles was inconsistent between gutter and no-gutter mode (c93752b)
• ui: field errors aren't red in light mode (7a4dd58)
• next,ui: fixes global doc permissions and optimizes publish access data loading (#6451) (2b941b7)
• richtext-lexical: link drawer sending too many form state requests for actions unrelated to links (0bfbf9c)
• ui: disableListColumn fields not hidden in table columns (#6445) (bcc506b)

BREAKING CHANGES

• next.js 15, react 19, react compiler support (#6429) (35f961f)

BREAKING:

• bumps minimum required next.js version from 14.3.0-canary.68 to
  15.0.0-rc.0
• bumps minimum required react and react-dom versions to 19.0.0 (19.0.0-rc-f994737d14-20240522 should be used)
• @types/react and @types/react-dom have to be bumped to
  npm:types-react@19.0.0-beta.2 using overrides and pnpm overrides, if
  you want correct types. You can find an example of this here:
  https://github.com/payloadcms/payload/pull/6429/files#diff-10cb9e57a77733f174ee2888587281e94c31f79e434aa3f932a8ec72fa7a5121L32

Issues

• Bunch of todos for our react-select package which is having type
  issues. Works fine, just type issues. Their type defs are importing JSX
  in a weird way, we likely just have to wait until they fix them in a
  future update.

• ui: uses consistent button naming conventions (#6444) (af7e12a)

Description

Renames the Save to SaveButton, etc. to match the already
established convention of the PreviewButton, etc. This matches the
imports with their respective component and type names, and also gives
these components more context to the developer whenever they're
rendered, i.e. its clearly just a button and not an entire block or
complex component.

BREAKING:

Import paths for these components have changed, if you were previously
importing these components into your own projects to customize, change
the import paths accordingly:

Old:

import { PublishButton } from '@payloadcms/ui/elements/Publish'
import { SaveButton } from '@payloadcms/ui/elements/Save'
import { SaveDraftButton } from '@payloadcms/ui/elements/SaveDraft'

New:

import { PublishButton } from '@payloadcms/ui/elements/PublishButton'
import { SaveButton } from '@payloadcms/ui/elements/SaveButton'
import { SaveDraftButton } from '@payloadcms/ui/elements/SaveDraftButton'

• I have read and understand the
  CONTRIBUTING.md
  document in this repository.

Contributors

• Alessio Gravili (@AlessioGr)
• Paul (@paulpopus)
• Jarrod Flesch (@JarrodMFlesch)
• Elliot DeNolf (@denolfe)
• Jacob Fletcher (@jacobsfletch)
• zvizvi (@zvizvi)
• Patrik (@PatrikKozak)

v3.0.0-beta.35

v3.0.0-beta.35 (2024-05-21)

Features

• store focal point on uploads (#6436) (36fda30)

Bug Fixes

• user verification email broken (#6442) (23f9a32)
• ui: blocks browser save dialog from opening when hotkey used with no changes (#6366) (0190eb8)
• separate sort and search fields when looking up relationship. (#6440) (f482fdc)
• ui: tooltip positioning issues (#6439) (ed47661)
• ui: update relationship cell formatted value when when search changes (#6208) (e682cb1)
• richtext-lexical: field required validation not working if content was removed manually (#6435) (fa7cc37)
• attributes graphql packages, adds esm import path (#6431) (1d81eef)
• plugin-seo: white screen of death on choosing an existing media for meta image (#6424) (8fcfac6)

BREAKING CHANGES

• export DefaultListView as ListView (#6432) (a8a2dc2)

Change the exports of DefaultListView and DefaultEditView to be renamed
without "Default" as ListView

// before
import { DefaultEditView } from '@payloadcms/next/views'
import { DefaultListView } from '@payloadcms/next/views'

// after 
import { EditView } from '@payloadcms/next/views'
import { ListView } from '@payloadcms/next/views'

Contributors

• Paul (@paulpopus)
• Alessio Gravili (@AlessioGr)
• Jessica Chowdhury (@JessChowdhury)
• Anders Semb Hermansen (@andershermansen)
• Ritsu (@r1tsuu)
• Elliot DeNolf (@denolfe)
• Jarrod Flesch (@JarrodMFlesch)

v3.0.0-beta.34

v3.0.0-beta.34 (2024-05-17)

Bug Fixes

• page metadata generation not working in turbopack (#6417) (147b50e)

Contributors

• Alessio Gravili (@AlessioGr)

v3.0.0-beta.33

v3.0.0-beta.33 (2024-05-17)

Features

• richtext-lexical: new aboveContainer and belowContainer plugin positioning options, fix incorrect placeholder positioning (#6410) (bf106db)
• upgrade minimum next version to 14.3.0-canary.68 & upgrade react packages, react-toastify (#6387) (9d5c0d3)
• allow client components and extra rsc props for custom edit and list views (#6395) (2762131)
• replaces admin.meta.ogImage with admin.meta.openGraph.images (#6227) (9556d1b)
• richtext-lexical: upgrade lexical from 0.14.5 to 0.15.0 (#6371) (fbea524)
• richtext-lexical: upgrade lexical from 0.14.5 to 0.15.0 and ensure peerDependencies force correct lexical version (22480a7)

Bug Fixes

• db-postgres: uuid custom db name (#6408) (c2571cf)
• db-postgres: query with like on id columns (#6414) (12c812d)
• ui: properly sets hasSavePermission on nested documents (#6394) (1800934)
• component is undefined error within isReactServerComponentOrFunction (#6411) (89b6055)
• turbopack RSC detection (#6405) (4dedd6e)
• next: removes initPage export from barrel file (#6403) (553bb4b)
• loader support for server-only (#6383) (5083525)
• react-select menu is hidden behind lexical fixed toolbar (#6396) (5323d76)
• richtext-lexical: upload, relationship and block node insertion fails sometimes (6083870)
• next: incorrect stepnav breadcrumbs after selecting existing upload (#6372) (a4deaf0)
• next: does not wrap custom views with template by default (#6379) (4adf01a)
• translations: type StripCountVariants not working in TS strict mode (#6374) (1abcdf9)
• safely access cookie header for uploads (#6373) (fbad39a)
• db-postgres: filter with ID not_in AND queries (#6359) (e8d1d36)
• loader throwing errors for client files imported using TS paths (#6369) (cb9a20f)
• richtext-lexical: autoLink node styles not inherited from original text node on creation (8db9664)
• multiselect relationship bug and improve accessibility (#6286) (5a4074e)

BREAKING CHANGES

• upgrade minimum next version to 14.3.0-canary.68 & upgrade react packages, react-toastify (#6387) (9d5c0d3)

BREAKING:

• The minimum required next version is now 14.3.0-canary.68. This is
  because we are migrating away from the deprecated
  experimental.serverComponentsExternalPackages next config key to
  experimental.serverExternalPackages, which is not available in older
  next canaries
• The minimum react and react-dom versions have been bumped to
  ^18.2.0 or ^19.0.0. This matches the minimum react version recommended
  by next

• next: removes initPage export from barrel file (#6403) (553bb4b)

• replaces admin.meta.ogImage with admin.meta.openGraph.images (#6227) (9556d1b)

• remove unused staticOptions config on uploads (#6378) (a6bf058)

Removes the unused staticOptions on upload config, it was previously
typed to express configuration and is unused anywhere in the codebase

• richtext-lexical: upgrade lexical from 0.14.5 to 0.15.0 (#6371) (fbea524)

BREAKING: This upgrades all lexical packages from 0.14.5 to 0.15.0.
If there are any breaking changes within lexical, this could break your
project if you use lexical APIs directly (e.g. in custom features). We
have not noticed any breaking changes within core. Please consult their
changelog: https://github.com/facebook/lexical/releases/tag/v0.15.0"

• richtext-lexical: upgrade lexical from 0.14.5 to 0.15.0 and ensure peerDependencies force correct lexical version (22480a7)

Contributors

• James Mikrut (@jmikrut)
• Dan Ribbens (@DanRibbens)
• Alessio Gravili (@AlessioGr)
• Jacob Fletcher (@jacobsfletch)
• Francis Turmel (@fturmel)
• Elliot DeNolf (@denolfe)
• Paul (@paulpopus)
• Patrik (@PatrikKozak)
• Jarrod Flesch (@JarrodMFlesch)
• Jessica Chowdhury (@JessChowdhury)

v2.18.3

2.18.3 (2024-05-17)

Bug Fixes

• db-postgres: query with like on id columns (#6416) (bf77cec)
• db-postgres: uuid custom db name (#6409) (db5f3f3)
• nested disableListColumn in rows (#6412) (ab8b2f3), closes #6407

v2.18.2

2.18.2 (2024-05-17)

Bug Fixes

• allow focal point when no sizes defined (#6397) (88e113a)

v2.18.1

2.18.1 (2024-05-16)

Bug Fixes

• add back explicit crop x and y values (#6391) (e76df32)

v2.18.0

2.18.0 (2024-05-16)

Features

• store focal point on uploads (#6364) (82b88a3)

Bug Fixes

• db-postgres: filter with ID not_in AND queries - postgres (#6358) (cc94078), closes #5151
• richtext-lexical: upload, relationship and block node insertion fails sometimes (#6390) (48a410e)

v2.17.0

2.17.0 (2024-05-15)

Features

• adds misc translations to API view and react select (#6138) (30e535b)

• richtext-lexical: remove LexicalBlock, RichTextFieldRequiredEditor and FieldWithRichTextRequiredEditor types (#6279) (9df5ab8)

Bug Fixes

• appends editDepth value to radio & checkbox IDs when inside drawer (#6181) (69c93d3)
• collection labels with locales not working when creating new doc (#5995) (51efe4f)
• safely access cookie header for uploads (#6367) (de92c50)
• step-nav breadcrumbs ellipsis (#6345) (d02b1fb)

⚠ BREAKING CHANGES

• richtext-lexical: remove LexicalBlock, RichTextFieldRequiredEditor and FieldWithRichTextRequiredEditor types (#6279)

3.0.0-beta.32

3.0.0-beta.32 (2024-05-14)

Features

• richtext-lexical: add rootFeatures prop to lexicalEditor (#6360) (c8a1cca)
• add missing server-only props to custom RSCs, improve req.user type, clean-up ui imports (#6355) (79f4907)
• consolidates admin.logoutRoute and admin.inactivityRoute into admin.routes (#6354) (6a0fffe)

Bug Fixes

• graphql: threads through correct draft value for upload relations (#6235) (6e116a7)

BREAKING CHANGES

• add missing server-only props to custom RSCs, improve req.user type, clean-up ui imports (#6355) (79f4907)

Previously, we were only passing payload to RSCs. Now, we are passing the following props for component rendered outside buildComponentMap:

• i18n,
• locale,
• params,
• payload,
• permissions,
• searchParams,
• user

And the following props for components rendered within buildComponentMap:

• i18n,
• payload,

Breaking:

if you use the following components in your own project, these now require aforementioned additional, server-only props, instead of just the payload prop:

• Account view
• Default Dashboard view
• DefaultTemplate
• WithServerSideProps
• RenderCustomComponent (optional)
• Logo

Additionally, if you were using an HOC as a custom component, and the HOC passed props to the client component, you now have to filter out the additional server-only props we provide. You can use our withMergedProps helper, which filters them automatically, >or mark your HOC with 'use client'.

• consolidates admin.logoutRoute and admin.inactivityRoute into admin.routes (#6354) (6a0fffe)

The admin.logoutRoute and admin.inactivityRoute properties have been consolidated into a single admin.routes property. To migrate, simply move those two keys as follows:

Old way:

// payload.config.ts
{ 
  // ...
  admin: {
    logoutRoute: '/custom-logout',
    inactivityRoute: '/custom-inactivity'
  }
}

New way:

// payload.config.ts
{
  // ...
  admin: {
    routes: {
      logout: '/custom-logout',
      inactivity: '/custom-inactivity'
    }
  }
}

Contributors

• Alessio Gravili (@AlessioGr)
• Jacob Fletcher (@jacobsfletch)
• Jarrod Flesch (@JarrodMFlesch)