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 from payload. 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
  the theme-elevation contrasts. Some adjustments to the Toast
  components as well to match light/dark mode better.