payload

v3.0.0-beta.46 (2024-06-12)

Features

• diff generated types before write (#6749) (be0462d)
• richtext-lexical: sub-field hooks and localization support (#6591) (4e12705)

Bug Fixes

• corrects block duplicate action and add tests (#6589) (763a34f)
• unawaited emails (#6265) (6e55a2e)
• ui: hideGutter was ignored in group field (#6613) (de45e60)
• add missing export for useLeaf hook (#6693) (74159de)
• list sort preferences (#6731) (ba92d86)

BREAKING CHANGES

• richtext-lexical: sub-field hooks and localization support (#6591) (4e12705)

BREAKING

• Our internal field hook methods now have new required schemaPath and
  path props. This affects the following functions, if you are using
  those: afterChangeTraverseFields, afterReadTraverseFields,
  beforeChangeTraverseFields, beforeValidateTraverseFields,
  afterReadPromise
• The afterChange field hook's value is now the value AFTER the
  previous hooks were run. Previously, this was the original value, which
  I believe is a bug
• Only relevant if you have built your own richText adapter: the
  richText adapter populationPromises property has been renamed to
  graphQLPopulationPromises and is now only run for graphQL. Previously,
  it was run for graphQL AND the rest API. To migrate, use
  hooks.afterRead to run population for the rest API
• Only relevant if you have built your own lexical features: The
  populationPromises server feature property has been renamed to
  graphQLPopulationPromises and is now only run for graphQL. Previously,
  it was run for graphQL AND the rest API. To migrate, use
  hooks.afterRead to run population for the rest API
• Serialized lexical link and upload nodes now have a new id property.
  While not breaking, localization / hooks will not work for their fields
  until you have migrated to that. Re-saving the old document on the new
  version will automatically add the id property for you. You will also
  get a bunch of console logs for every lexical node which is not migrated

Contributors

• Jessica Chowdhury (@JessChowdhury)
• Elliot DeNolf (@denolfe)
• Alessio Gravili (@AlessioGr)
• Anders Semb Hermansen (@andershermansen)
• Patryk Kowalczyk (@Patryk-Kowalczyk)
• Jarrod Flesch (@JarrodMFlesch)

2.20.0 (2024-06-11)

Features

• ui: updates draft/published version pills (#6732) (ed86b15)

Bug Fixes

• adds multi select inputs for number & text fields in where builder (#6662) (e3003b4)
• create sharp file for fileHasAdjustments files or fileIsAnimated files (#6710) (921a5c0)
• enable SaveDraft button when creating new documents (#6672) (63bc6ae), closes #6671
• handles localized nested relationship fields in versions (#6679) (8a62298)
• live preview device position when using zoom (#6667) (9525511)
• only use metadata.pages for height if animated (#6729) (2f9ed34)
• removes array & blocks & group fields from sort (#6574) (507e095), closes #6469
• withinCollapsible should be undefined by default (#6666) (37c8386), closes #6658

v3.0.0-beta.45 (2024-06-11)

Features

• move from react-toastify to sonner (#6682) (cb3355b)

Bug Fixes

• toasts padding and button placement by 1px (#6730) (2ada6fc)
• only use metadata.pages for height if animated (#6728) (10c6ffa)
• create sharp file for fileHasAdjustments files or fileIsAnimated files (#6708) (6512d5c)
• corrects field-paths that were incorrectly being set (#6724) (57fcc91)

BREAKING CHANGES

• move from react-toastify to sonner (#6682) (cb3355b)

We now export toast from sonner instead of
react-toastify. If you send out toasts from your own projects, make
sure to use our toast export, or install sonner. React-toastify
toasts will no longer work anymore. The Toast APIs are mostly similar,
but there are some differences if you provide options to your toast

CSS styles have been changed from Toastify

/* before */
.Toastify


/* current */
.payload-toast-container
.payload-toast-item
.payload-toast-close-button

/* individual toast items will also have these classes depending on the state */
.toast-info
.toast-warning
.toast-success
.toast-error

https://github.com/payloadcms/payload/assets/70709113/da3e732e-aafc-4008-9469-b10f4eb06b35

Contributors

• Paul (@paulpopus)
• Alessio Gravili (@AlessioGr)
• Patrik (@PatrikKozak)
• Jarrod Flesch (@JarrodMFlesch)

v3.0.0-beta.44 (2024-06-11)

Features

• type auto-generation (#6657) (7309d47)

Bug Fixes

• get auto type-gen to work on turbo, by running type gen in a child process outside turbo/webpack (#6714) (7b7dc71)
• corrects tab paths when nested within other row like fields (#6712) (ba513d5)
• re-exports graphql json types for external use (#6711) (a26d031)
• ui: removes array & blocks & group fields from sort (#6576) (9f52562)
• global draft validations (#6709) (45e8683)
• ui: set checkbox htmlFor by default, fixing some checkbox labels not toggling the checkbox (#6684) (ac34380)

BREAKING CHANGES

• type auto-generation (#6657) (7309d47)

Types are now auto-generated by default.

You can opt-out of this behavior by setting:

buildConfig({
  // Rest of config
  typescript: {
    autoGenerate: false
  },
})

Contributors

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

v3.0.0-beta.43 (2024-06-07)

Features

• adds draft validation option (#6677) (52c81ad)
• plugin-redirects: update fields overrides to use a function (#6675) (e4a9029)
• richtext-*: allow omitting the root editor property (#6660) (11c3a65)
• upgrade minimum node 20 version from 20.6.0 to 20.9.0 (#6659) (9bd9e7a)

Bug Fixes

• next: live preview device position when using zoom (#6665) (7c8d562)
• max versions config not being respected on globals (#6654) (8dd5e4d)

BREAKING CHANGES

• plugin-redirects: update fields overrides to use a function (#6675) (e4a9029)

Description

Updates the fields override in plugin redirects to allow for
overriding

// before
overrides: {
  fields: [
    {
      type: 'text',
      name: 'customField',
    },
  ],
},

// current
overrides: {
  fields: ({ defaultFields }) => {
    return [
      ...defaultFields,
      {
        type: 'text',
        name: 'customField',
      },
    ]
  },
},

• upgrade minimum node 20 version from 20.6.0 to 20.9.0 (#6659) (9bd9e7a)

• This bumps the minimum required node version from node 20.6.0 to node
  20.9.0. This is because 20.6.0 breaks type generation due to a CJS node
  bug, and 20.9.0 is the next v20 LTS version. The minimum node 18 version
  stays the same (18.20.2)

Contributors

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

2.19.3 (2024-06-07)

Bug Fixes

• scopes uploadEdits to documents, hoists action to doc provider (#6664) (373cb00)

v3.0.0-beta.42 (2024-06-06)

Bug Fixes

• ui: global documents disabled after save (#6652) (267c236)

Contributors

• Jacob Fletcher (@jacobsfletch)
• Alessio Gravili (@AlessioGr)

2.19.2 (2024-06-06)

Bug Fixes

• cascade draft arg when querying globals with graphql (#6651) (ac8c209)
• filtered out disableListColumn fields reappeared after toggling other fields (#6636) (626be15)
• resizing animated images (#6621) (67c0b0e), closes #2181 #6146

v3.0.0-beta.41 (2024-06-05)

Features

• support Next.js basePath config property (#6628) (b2751f7)
• ui: expose RowLabelProps (#6627) (1afd221)
• richtext-lexical: upgrade lexical from 0.15.0 to 0.16.0 and port over relevant playground changes (#6620) (da35afb)

Bug Fixes

• db-postgres: create predefined migration missing json schema output (#6641) (ff82bb5)
• update file-type dependency and fix dependency version mismatch (#6638) (2077da8)
• translations: explicitly declare date-fns v3 as a dependency (#6626) (aeb4df8)
• resizing animated images (#6623) (bcd277e)
• migration file cannot be imported (#6616) (cafc13a)

BREAKING CHANGES

• db-postgres: create predefined migration missing json schema output (#6641) (ff82bb5)

Fixes #6630

This only applies to you if you using db-postgres and have created the
v2-v3-relationships migration released in
v3.0.0-beta.39
from @payloadcms/db-postgres <= v3.0.0-beta.40.

Steps to fix

• Delete the existing v2-v3-relationships migration file.
• If changes were made to your config since the previous migration was
  made, you will need to revert those by checking out a previous commit in
  your version control.
• Recreate the migration using payload migrate:create --file @payloadcms/db-postgres/relationships-v2-v3 to make the migration with
  the snapshot .json file.

• richtext-lexical: upgrade lexical from 0.15.0 to 0.16.0 and port over relevant playground changes (#6620) (da35afb)

BREAKING:

• This upgrades the required version of lexical from 0.15.0 to 0.16.0.
  If you are using lexical directly in your project, possibly due to
  custom features, there might be breaking changes for you. Please consult
  the lexical 0.16.0 changelog:
  https://github.com/facebook/lexical/releases/tag/v0.16.0

Contributors

• Dan Ribbens (@DanRibbens)
• Alessio Gravili (@AlessioGr)
• Elliot DeNolf (@denolfe)
• Jacob Fletcher (@jacobsfletch)
• Patrik (@PatrikKozak)
• Paul (@paulpopus)

2.19.1 (2024-06-04)

Bug Fixes

• payload/bundler-webpack: override ajv dependency version to 8.14.0 wherever possible (#6618) (e44ce81)

2.19.0 (2024-06-04)

Features

• translations: update Turkish translations (#5738) (4fddea8)

Bug Fixes

• pin ajv to 8.14.0, as 8.15.0 is broken (#6607) (4a54aa7)
• adds new userEmailAlreadyRegistered translations (#6549) (56c6700), closes #6535
• adjusts sizing of remove/add buttons to be same size (#6527) (a352ebc), closes #6098
• focalPoint undefined handling (#6552) (fcfc3c5)
• pagination on polymorphic relationship field requesting entries with page parameter set to NaN (#5366) (547acfe)
• safely evaluates field.admin in WhereBuilder (#6534) (4f9d78d)
• separate sort and search fields when looking up relationship. (#5964) (c009219), closes #4815 #5222
• ui field validation error with admin.disableListColumn property (#6530) (eeddece), closes #6521
• ui: blocks browser save dialog from opening when hotkey used with no changes (#6365) (8f03cd7), closes #214

v3.0.0-beta.40 (2024-06-04)

Features

• match next.js env file loading behavior in bin scripts & importConfig, clean up installed packages & mismatching package versions (#6601) (59cde0d)
• richtext-lexical: configurable fixed toolbar (#6560) (f41bb05)

Bug Fixes

• pin ajv to 8.14.0, as 8.15.0 is broken (#6606) (45b02d8)
• plugin-form-builder: fix bug with optional chain operator in field overrides logic (#6602) (1aece39)
• db-postgres: type issue in migratePostgresV2toV3 call if ts strict mode is enabled (#6585) (c3589de)
• richtext-lexical: minor design improvements (#6575) (c7fbd76)
• critical getPredefinedMigration dependency error (#6578) (6b9c796)
• richtext-*: fix client features were not loaded properly, improve performance of LexicalProvider, slate cell component was non-functional, support richtext adapter Cell RSCs (#6573) (5cb49c3)

BREAKING CHANGES

• richtext-lexical: configurable fixed toolbar (#6560) (f41bb05)

BREAKING: useEditorFocusProvider has been removed and merged with
useEditorConfigContext. You can now find information about the focused
editor, parent editors and child editors within useEditorConfigContext

Contributors

• Alessio Gravili (@AlessioGr)
• Paul (@paulpopus)

v3.0.0-beta.39 (2024-05-30)

Features

• db-postgres: relationship column (#6339) (edfa85b)

Bug Fixes

• next: ssr live preview was not dispatching document save events (#6572) (e603c83)

BREAKING CHANGES

• db-postgres: relationship column (#6339) (edfa85b)

BREAKING CHANGE:

Moves upload field and relationship fields with hasMany: false &
relationTo: string from the many-to-many _rels join table to simple
columns. This only affects Postgres database users.

TL;DR

We have dramatically simplified the storage of simple relationships in
relational databases to boost performance and align with more expected
relational paradigms. If you are using the beta Postgres adapter, and
you need to keep simple relationship data, you'll need to run a
migration script that we provide you.

Background

For example, prior to this update, a collection of "posts" with a simple
hasMany: false and relationTo: 'categories' field would have a
posts_rels table where the category relations would be stored.

This was somewhat unnecessary as simple relations like this can be
expressed with a category_id column which is configured as a foreign
key. This also introduced added complexity for dealing directly with the
database if all you have are simple relations.

Who needs to migrate

You need to migrate if you are using the beta Postgres database adapter
and any of the following applies to you.

• If you have versions enabled on any collection / global
• If you use the upload field
• If you have relationship fields that are hasMany: false (default)
  and relationTo to a single category (has
  one) relations

We have a migration for you

Even though the Postgres adapter is in beta, we've prepared a predefined
migration that will work out of the box for you to migrate from an
earlier version of the adapter to the most recent version easily.

It makes the schema changes in step with actually moving the data from
the old locations to the new before adding any null constraints and
dropping the old columns and tables.

How to migrate

The steps to preserve your data while making this update are as follows.
These steps are the same whether you are moving from Payload v2 to v3 or
a previous version of v3 beta to the most recent v3 beta.

Important: during these steps, don't start the dev server unless you
have push: false set on your Postgres adapter.

Step 1 - backup

Always back up your database before performing big changes, especially
in production cases.

Step 2 - create a pre-update migration

Before updating to new Payload and Postgres adapter versions, run
payload migrate:create without any other config changes to have a
prior snapshot of the schema from the previous adapter version

Step 3 - if you're migrating a dev DB, delete the dev push row

from your payload_migrations table

If you're migrating a dev database where you have the default setting to
push database changes directly to your DB, and you need to preserve data
in your development database, then you need to delete a dev migration
record from your database.

Connect directly to your database in any tool you'd like and delete the
dev push record from the payload_migrations table using the following
SQL statement:

DELETE FROM payload_migrations where batch = -1

Step 4 - update Payload and Postgres versions to most recent

Update packages, making sure you have matching versions across all
@payloadcms/* and payload packages (including
@payloadcms/db-postgres)

Step 5 - create the predefined migration

Run the following command to create the predefined migration we've
provided:

payload migrate:create --file @payloadcms/db-postgres/relationships-v2-v3

Step 6 - migrate!

Run migrations with the following command:

payload migrate

Assuming the migration worked, you can proceed to commit this change and
distribute it to be run on all other environments.

Note that if two servers connect to the same database, only one should
be running migrations to avoid transaction conflicts.

Related discussion:
https://github.com/payloadcms/payload/discussions/4163

Contributors

• Elliot DeNolf (@denolfe)
• Dan Ribbens (@DanRibbens)
• Jacob Fletcher (@jacobsfletch)

v3.0.0-beta.38 (2024-05-30)

Features

• next,ui: improves loading states (#6434) (92f458d)
• extracts buildFormState logic from endpoint for reuse (#6501) (321e97f)

Bug Fixes

• cpa: safer command exists check (#6569) (4884f0d)
• ui: adjusts sizing of remove/add buttons to be same size (#6529) (f1db24e)
• ui field validation error with admin.disableListColumn property (#6531) (7f15147)
• translations: adds new userEmailAlreadyRegistered translations (#6550) (e0a6db7)
• cpa: more package manager detection improvements (#6566) (0d7d3e5)
• duplicate options appearing in relationship where builder (#6557) (3474642)
• plugin-search: Render error on custom UI component (#6562) (aa02801)
• ensure relationship field pills respect isSortable property (#6561) (425576b)
• ability to query relationships not equal to ID (#6555) (043a91d)

Contributors

• Elliot DeNolf (@denolfe)
• Patrik (@PatrikKozak)
• Jarrod Flesch (@JarrodMFlesch)
• Paul (@paulpopus)
• Jessica Chowdhury (@JessChowdhury)
• Jacob Fletcher (@jacobsfletch)

v3.0.0-beta.37 (2024-05-29)

Features

• richtext-lexical: link markdown transformers (#6543) (33d5312)
• richtext-lexical: i18n (#6542) (a8000f6)
• plugin-form-builder: update form builder plugin field overrides to use a function instead (#6497) (7d0e909)
• cpa: update existing payload installation (#6193) (10c94b3)
• richtext-lexical: i18n support (#6524) (c383f39)
• richtext-lexical: update validation of custom URLs to include relative and anchor links (#6525) (8a91a7a)

Bug Fixes

• cpa: improve package manager detection (#6546) (8506385)
• multi value draggable/sortable pills (#6500) (e749529)
• richtext-lexical: various html converter fixes (#6544) (4a51f4d)
• richtext-lexical: user-defined html converters not taking precedence, and shared default html converters doubling in size after every field initialization (2c283bc)
• richtext-lexical: list converters and nodes being added duplicatively (a2e9bcd)
• richtext-lexical: link html converter: serialize newTab to target="_blank" (#6350) (e0b201c)
• deps: proper location for scheduler peer dep (#6537) (2ddd50e)
• Add missing He lang export in payload/i18n (#6484) (6f5d86e)
• next: unable to pass custom view client components (#6513) (eff5129)
• separate collection docs with same ids were excluded in selectable (#6499) (18bc4b7)
• richtext-lexical: localized sub-fields were omitted from the API output (#6489) (7a76814)
• ui: where builder issues (#6478) (42222cd)

BREAKING CHANGES

• plugin-form-builder: update form builder plugin field overrides to use a function instead (#6497) (7d0e909)

Changes the fields override for form builder plugin to use a function
instead so that we can actually override existing fields which currently
will not work.

//before
fields: [
  {
    name: 'custom',
    type: 'text',
  }
]

// current
fields: ({ defaultFields }) => {
  return [
    ...defaultFields,
    {
      name: 'custom',
      type: 'text',
    },
  ]
}

Contributors

• Elliot DeNolf (@denolfe)
• Jarrod Flesch (@JarrodMFlesch)
• Alessio Gravili (@AlessioGr)
• Leo Hilsheimer (@linobino1)
• Paul (@paulpopus)
• zvizvi (@zvizvi)
• Dan Ribbens (@DanRibbens)
• Patrik (@PatrikKozak)

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:[email protected] 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 (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 (2024-05-17)

Bug Fixes

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

Contributors

• Alessio Gravili (@AlessioGr)

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)

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