Payload CMS Release: Release 1.8.3

TL;DR

Payload CMS v1.8.3: Relationship Improvements & Critical Bug Fixes

This release focuses on fixing several critical issues with relationships, draft documents, and GraphQL queries. Mobile users will benefit from improved relationship field interactions, while developers will appreciate the fixes for document querying and relationship handling. The update also includes documentation improvements and translation refinements.

Highlight of the Release

• Fixed relationship handling on mobile devices
• Corrected GraphQL querying for relationships with custom IDs
• Fixed draft document querying by ID
• Prevented duplicate values when adding relationships through modals
• Added credentials to document access requests

Migration Guide

Migration from v1.8.2 to v1.8.3

This is a patch release with no breaking changes. You can upgrade safely by updating your package.json:

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

Note on React Select

This release migrates to React Select v5.7.3. If you have custom components that extend or modify React Select functionality, you may need to update your implementation to match the new version.

Upgrade Recommendations

This release is highly recommended for all users, especially those who:

• Use relationship fields in their content models
• Have mobile users managing content
• Use GraphQL for querying relationships or draft documents
• Have implemented custom ID fields

The fixes in this release address several critical issues that could affect data integrity and user experience, particularly around relationship handling and document querying.

Bug Fixes

Relationship Improvements

• Fixed issues with clearing relationships or opening relationship drawers on mobile devices (#2691, #2692)
• Prevented relationship modals from adding duplicate values to parent documents (#2688)
• Improved handling of externally updated relationships
• Fixed relationship drawer save functionality

GraphQL and Query Fixes

• Fixed GraphQL querying for relationships with custom IDs (#2685)
• Corrected draft document querying by ID (#2662)
• Added proper credentials to document access requests (#2705)
• Fixed GraphQL parameter types, correcting the id type from JSON to String

UI and Style Fixes

• Fixed modal overflow caused by unused button tooltips (#2676)
• Fixed disabled select fields styling
• Improved React Select styles after migration to v5.7.3
• Fixed Slate editor not reinitializing after row changes (#2647)

New Features

New Multi-tenant Example

A new multi-tenant example has been added to the Payload CMS repository, demonstrating how to implement multi-tenancy in your Payload applications. This example provides a practical reference for developers looking to build applications that serve multiple clients or organizations from a single codebase.

Security Updates

Security Enhancements

• Added credentials to document access requests (#2705), ensuring proper authentication context is maintained during requests
• Safely validates null relations to prevent potential security issues
• Improved error logging for email sending functionality

Performance Improvements

Performance Optimizations

• Improved relationship field handling which reduces unnecessary re-renders
• Optimized document access requests by properly including credentials
• Enhanced GraphQL query performance for relationships with custom IDs
• Streamlined React Select implementation with migration to v5.7.3

Impact Summary

Payload CMS v1.8.3 delivers significant improvements to relationship field handling, particularly on mobile devices, while fixing critical issues with GraphQL queries and draft document handling. The release enhances the stability and reliability of the CMS, with special attention to relationship fields which are central to content modeling in Payload.

The fixes for mobile relationship interactions (#2691, #2692) improve the content editing experience for users on tablets and smartphones, addressing frustrating issues that prevented proper relationship management. GraphQL query fixes (#2685, #2662) ensure that developers can reliably query related content and draft documents, which is essential for building dynamic frontend applications.

Documentation improvements, including REST API examples and updated installation guides, help new developers get started more easily. The addition of a multi-tenant example provides valuable guidance for developers building more complex applications.

Overall, this release represents an important maintenance update that enhances stability, fixes user experience issues, and improves documentation without introducing breaking changes.

Full Release Notes