Releases: payloadcms/payload
v3.0.0-beta.67
v3.0.0-beta.67 (2024-07-18)
Bug Fixes
Contributors
- Alessio Gravili (@AlessioGr)
- Patrik (@PatrikKozak)
- Jarrod Flesch (@JarrodMFlesch)
v3.0.0-beta.66
v3.0.0-beta.66 (2024-07-18)
Features
- ability to login with email, username or both (#7086) (7b3b021)
- add db idType to generated payload types (#7186) (502548a)
- richtext-lexical: inline blocks (#7102) (676dfa3)
- next: strongly type getNextRequestI18n (#7157) (c6da04a)
Bug Fixes
- cherry picks lockUntil fix from #6052 (#7213) (478fb8d)
- aliases AfterMe, AfterLogout, and AfterRefresh hook types (#7216) (700baf1)
- templates: bad import in website seed script (#7198) (a3af360)
- maxListenersExceeded warning due to atomically, which is a peerdep of conf (#7182) (1fe6761)
- ui: search queries remain between navigation (#7169) (f909f06)
- richtext-lexical: slash menu keyboard navigation not triggering auto-scroll (#7185) (fe23ca5)
- webpack error if dbName or enumName was set (#7184) (8fdd88b)
- ui: date field background color specificity (#7181) (1ea2e32)
- version comparison view showing empty localized fields (#7180) (8fb17c2)
- localised relationship fields (#7178) (2f0aa83)
BREAKING CHANGES
Duplicate of #7146 but for beta. If you were using the AfterMeHook
, AfterLogoutHook
, or AfterRefreshHook
, these types have been renamed and are now prefixed with Collection
to match all other hook naming conventions, just as the documentation already indicates.
Old:
import type { AfterMeHook, AfterLogoutHook, AfterRefreshHook } from 'payload'
New:
import type { CollectionAfterMeHook, CollectionAfterLogoutHook, CollectionAfterRefreshHook } from 'payload'
Contributors
- Jarrod Flesch (@JarrodMFlesch)
- Jacob Fletcher (@jacobsfletch)
- Paul (@paulpopus)
- Alessio Gravili (@AlessioGr)
- Jessica Chowdhury (@JessChowdhury)
v2.24.0
v3.0.0-beta.65
v3.0.0-beta.65 (2024-07-15)
Features
Bug Fixes
- richtext-lexical: newly created upload nodes with extra fields do not display fields when opening extra fields drawer (#7155) (35f7a9e)
- richtext-*: nested field recursion for named tabs did not work (8c5a1f0)
- richtext-lexical: one-line migrators not detecting richText migrations in nested fields (6d68a4a)
- email-nodemailer: skipVerify behavior being reversed (#6790) (f494eba)
- custom tabs not working in globals (#7148) (24f55c9)
Contributors
- Alessio Gravili (@AlessioGr)
- Jacob Fletcher (@jacobsfletch)
- Hulpoi George-Valentin (@GeorgeHulpoi)
- Jasper Beaurain (@JasperBeaurain)
- Jarrod Flesch (@JarrodMFlesch)
- Paul (@paulpopus)
v3.0.0-beta.63
v3.0.0-beta.63 (2024-07-12)
Fixes publishing issue
v3.0.0-beta.62
v3.0.0-beta.62 (2024-07-12)
Features
- validate field names for reserved names (#7130) (03d854e)
- ui: various admin panel styling improvements (#7121) (c359c34)
- suppress email adapter warning on build (#7129) (b750ebf)
- ui: updates version status UI to be more informative (#6661) (c019969)
- richtext-lexical: add missing SerializedLineBreakNode to default node types, remove SerializedBlockNode from default node types (1c8bed5)
- richtext-lexical: allow SerializedBlockNode fields to be typed via generic (10336ba)
Contributors
- Paul (@paulpopus)
- Tylan Davis (@tylandavis)
- Jacob Fletcher (@jacobsfletch)
- Elliot DeNolf (@denolfe)
- Alessio Gravili (@AlessioGr)
- Jessica Chowdhury (@JessChowdhury)
v3.0.0-beta.61
v3.0.0-beta.61 (2024-07-12)
Features
- upgrade minimum react, react-dom, @types/react and @types/react-dom versions to match exactly what Next.js is using, various dependency cleanup (#7106) (f86e0ed)
- adds ability to upload files from a remote url (#7063) (d99bff9)
Bug Fixes
- ui: ctrl+s not triggering a save if autosave is enabled (#7120) (840e075)
- templates: website template gitignore issue for case sensitivity (#7118) (1baf775)
- richtext-lexical: export types as type-only exports (#7097) (edf743e)
BREAKING CHANGES
- upgrade minimum react, react-dom, @types/react and @types/react-dom versions to match exactly what Next.js is using, various dependency cleanup (#7106) (f86e0ed)
BREAKING:
- Upgrades minimum supported @types/react version from
npm:[email protected] to npm:[email protected]- Upgrades minimum supported @types/react-dom version from
npm:[email protected] to npm:[email protected]- Upgrades minimum supported react and react-dom version from
19.0.0-rc-f994737d14-20240522 to 19.0.0-rc-6230622a1a-20240610
Contributors
- Jacob Fletcher (@jacobsfletch)
- Paul (@paulpopus)
- Elliot DeNolf (@denolfe)
- Alessio Gravili (@AlessioGr)
- Jarrod Flesch (@JarrodMFlesch)
- Patrik (@PatrikKozak)
v3.0.0-beta.60
v3.0.0-beta.60 (2024-07-10)
Features
- plugin-search: make search collection fields override into a function that provides defaultFields inline with other plugins (#7095) (2bc8666)
- cpa: add website template to CPA (#7079) (c1c12bc)
- replace qs with qs-esm (#6966) (6c99326)
- storage-azure: expose storage client (#7069) (f46ea01)
- richtext-lexical: remove unused json-schema dependency (#7072) (376a651)
- updated admin panel color palette (#7011) (c2022f6)
Bug Fixes
- ui: tooltips for fields rendered outside RenderFields not positioned correctly (#7074) (bd5f5a2)
- exports getSiblingData, getDataByPath, and reduceFieldsToValues from payload (#7070) (0a2ecf8)
- graphql query concurrency issues (#6925) (fb72d19)
- plugin-form-builder: make fields optional type in overrides (#7062) (cd9df73)
- plugin-redirects: make fields optional type in overrides (#7061) (b7acfe5)
BREAKING CHANGES
-
plugin-search: make search collection fields override into a function that provides defaultFields inline with other plugins (#7095) (2bc8666)
searchPlugin's searchOverrides for the collection now takes in a fields
function instead of array similar to other plugins and patterns we use
to allow you to map over existing fields as well if needed.// before searchPlugin({ searchOverrides: { slug: 'search-results', fields: [ { name: 'excerpt', type: 'textarea', admin: { position: 'sidebar', }, }, ] }, }), // current searchPlugin({ searchOverrides: { slug: 'search-results', fields: ({ defaultFields }) =[ ...defaultFields, { name: 'excerpt', type: 'textarea', admin: { position: 'sidebar', }, }, ] }, }),
-
exports getSiblingData, getDataByPath, and reduceFieldsToValues from payload (#7070) (0a2ecf8)
Exports
getSiblingData
,getDataByPath
,reduceFieldsToValues
, and
unflatten
frompayload
. These utilities were previously accessible
using direct import paths from@payloadcms/ui
—but this is no longer
advised since moving to a pre-bundled UI library pattern. Instead of
simply exporting these from the@payloadcms/ui
package, these exports
have been moved to Payload itself to provision for use outside of React
environments.This is considered a breaking change. If you were previously importing
any of these utilities, the imports paths have changed as follows:Old:
import { getSiblingData, getDataByPath, reduceFieldsToValues } from '@payloadcms/ui/forms/Form' import { unflatten } from '@payloadcms/ui/utilities'
New:
import { getSiblingData, getDataByPath, reduceFieldsToValues, unflatten } from 'payload/shared'
The
is-buffer
dependency was also removed in this PR. -
updated admin panel color palette (#7011) (c2022f6)
Color values have changed and will have different
contrasts. If you use any of Payload's colors in your apps, you may need
to adjust your use of them to maintain proper styling/accessibility.Colors palettes changed:
--theme-success-*
--theme-error-*
--theme-warning-*
--color-success-*
--color-error-*
--color-warning-*
--color-blue-*
Updates the color palette used throughout Payload to be more consistent
between dark and light values. Contrast values are now more in line with
thetheme-elevation
contrasts. Some adjustments to the Toast
components as well to match light/dark mode better.
v3.0.0-beta.59
v3.0.0-beta.59 (2024-07-08)
Features
- support latest Next.js versions, fix server-only props being passed to Client Document Views (#7026) (1cf7d4d)
- ui: support nested tabs, groups, collapsibles and rows in where filters in list view (#7044) (b6d85f6)
- avoid unnecessary config await in getPayloadHMR (#7045) (187813e)
Bug Fixes
- richtext-lexical: avoid conflicts between internal component/schema map paths and field names (#7042) (16c1d94)
BREAKING CHANGES
- support latest Next.js versions, fix server-only props being passed to Client Document Views (#7026) (1cf7d4d)
BREAKING: The minimum required Next.js version has been bumped from
15.0.0-rc.0
to15.0.0-canary.53
. This is because the way client
components are represented changed somewhere between those versions, and
it is not feasible to support both versions in our RSC detection logic.
Contributors
- Alessio Gravili (@AlessioGr)
- Wilson (@WilsonLe)
- Paul (@paulpopus)
v3.0.0-beta.58
v3.0.0-beta.58 (2024-07-03)
Features
- richtext-lexical: add EXPERIMENTAL_TableFeature, allow Client Features to register providers (#7010) (93bdc0e)
Bug Fixes
Contributors
- Jacob Fletcher (@jacobsfletch)
- Alessio Gravili (@AlessioGr)
- Jarrod Flesch (@JarrodMFlesch)