TL;DR

PayloadCMS v1.13.0 brings several quality-of-life improvements to the developer and admin experience. Tab labels now default to field names, radio and select fields are filterable by options, and JWT field support is now recursive. Several bugs were fixed including issues with block configurations, admin thumbnails, and type definitions. This release focuses on enhancing usability and fixing edge cases without introducing breaking changes.

Highlight of the Release

• Tab labels now default from field names for better usability
• Radio and select fields are now filterable by their options
• Added recursive support for fields in JWT tokens
• Fixed issues with block configurations and admin thumbnails
• Improved documentation with images for each field type

Migration Guide

No migration steps are required for this release. All changes are backward compatible and should work with existing PayloadCMS implementations without modification.

If you're using TypeScript and the setPreference() function, you may benefit from the improved type definitions, but no code changes are necessary.

Upgrade Recommendations

This release is recommended for all PayloadCMS users as it includes several quality-of-life improvements and bug fixes without introducing breaking changes. The enhancements to tab labels, field filtering, and JWT support provide meaningful improvements to both developer and admin experiences.

To upgrade, simply update your PayloadCMS dependency to version 1.13.0:

npm install [email protected]
# or
yarn add [email protected]

Bug Fixes

Fixed setPreference() Return Type

Corrected the TypeScript return type definition for the setPreference() function, improving type safety and developer experience.

Fixed Admin Thumbnails with Absolute staticURL

Resolved an issue where admin thumbnails weren't displaying correctly when using absolute paths in the staticURL configuration.

Fixed Block Configuration Handling

Fixed a bug where adding and replacing similarly shaped block configurations was causing issues. This ensures more reliable block management in the admin interface.

Fixed Form-Builder Example

Corrected the example for buildInitialFormState in the form-builder documentation, providing developers with accurate implementation guidance.

New Features

Default Tab Labels from Field Names

Tab labels now automatically default from the field name when not explicitly provided. This improves the admin interface usability by providing more intuitive labels without requiring additional configuration.

Filterable Radio and Select Fields

Radio and select fields can now be filtered by their options, enhancing the search and filter capabilities in the admin panel. This makes it easier to find specific content based on field values.

Recursive saveToJWT Field Support

The saveToJWT functionality now supports recursive fields, allowing for more complex data structures to be stored in JWT tokens. This enables more sophisticated authentication and authorization patterns.

Security Updates

No security fixes were mentioned in this release.

Performance Improvements

No specific performance improvements were highlighted in this release. The changes focus primarily on feature enhancements, bug fixes, and documentation improvements.

Impact Summary

PayloadCMS v1.13.0 delivers several meaningful improvements to both the developer and admin user experience. The introduction of default tab labels from field names reduces configuration overhead while improving interface clarity. The ability to filter radio and select fields by options enhances content management capabilities. Recursive JWT field support expands authentication possibilities.

Bug fixes address several edge cases including issues with block configurations, admin thumbnails with absolute URLs, and type definitions. The documentation has been enhanced with images for each field type, making it easier for developers to understand and implement field types correctly.

Overall, this release represents a solid incremental improvement that enhances usability without requiring migration efforts. The changes are particularly beneficial for developers building complex forms and for admin users who work with filtering and organization of content.

Full Release Notes