Change8

Payload CMS

Backend & Infra

Payload is the open-source, fullstack Next.js framework, giving you instant backend superpowers. Get a full TypeScript backend and admin panel instantly. Use Payload as a headless CMS or for building powerful applications.

Latest: v3.88.025 releases3 breaking changes6 common errorsView on GitHub

Release History

View all versions →
v3.88.02 fixes
Aug 11, 2026

This release includes bug fixes for multipart content-type handling and UI clipboard operations. It also refactors access control defaults for API keys in the plugin-mcp and updates Next.js to version 16.3.0.

v3.87.16 fixes
Aug 6, 2026

This release includes several bug fixes, including improvements to Next.js HMR endpoint connectivity, security updates for mongoose and @modelcontextprotocol/sdk, and enhancements to the richtext-lexical plugin. It also addresses build issues in the with-cloudflare-d1 template.

v3.87.017 fixes1 feature
Jul 31, 2026

This release enhances Azure storage capabilities for large files and includes numerous bug fixes across various modules, including database handling, UI elements, and plugins. Documentation has also been updated.

v3.86.08 fixes3 features
Jul 10, 2026

This release introduces collection-level bulk delete disabling and improves translation support in the form builder plugin. It also includes several bug fixes across various components, including UI, SDK, and multi-tenant functionality.

v3.85.215 fixes
Jul 1, 2026

This patch addresses numerous bugs across core functionality, database integrations (MongoDB, Drizzle), UI components, and plugins like cloud-storage. It also resolves several high-severity dependency vulnerabilities.

v3.85.17 fixes
Jun 9, 2026

Payload v3.85.1 is a patch release that fixes several bugs related to draft saving, CSV imports, and UI rendering conditions, alongside minor performance enhancements.

v3.85.012 fixes1 feature
May 26, 2026

This release promotes the import-export plugin to stable with hook support and includes numerous bug fixes across plugins and the UI, alongside dependency updates for security.

v3.84.1
Apr 23, 2026

This patch release primarily adjusts CI configurations to retarget the create-payload-app tool to use the 3.x branch.

v4.0.0-beta.0
Apr 22, 2026
v3.84.09 fixes5 features
Apr 22, 2026

Version v3.84.0 introduces features like client component support for custom collection views and enhanced configuration for email recipients. It also resolves several bugs related to localized field errors, multipart uploads, and UI field handling.

v3.83.02 fixes12 features
Apr 15, 2026

Version v3.83.0 introduces significant enhancements to plugin architecture with `definePlugin`, adds performance profiling tools, and brings UUIDv7 support to Drizzle adapters. It also includes experimental features like Lexical node view overrides and custom collection views in the Next.js admin.

v3.82.12 fixes
Apr 9, 2026

This patch release primarily addresses bug fixes in Next.js integration and the nested-docs plugin, alongside a performance improvement for S3 storage.

v3.82.026 fixes7 features
Apr 8, 2026

This release introduces features like query parameter disambiguation for media files and a new TypeScript post-process hook. It also includes numerous bug fixes across storage plugins, database integrations (MongoDB, Drizzle), UI components, and internationalization.

v3.81.019 fixes2 features
Apr 1, 2026

This release introduces an LLM evaluation suite and fixes several bugs across database integrations (MongoDB, Postgres), UI components, and Next.js compatibility. Dependency updates were also performed to address security vulnerabilities.

v3.80.014 fixes1 feature
Mar 20, 2026

Version v3.80.0 introduces configuration for unique slugs in multi-tenant setups and resolves numerous bugs across database drivers (MongoDB, Postgres, SQLite, Drizzle) and UI components.

v3.79.123 fixes1 feature
Mar 16, 2026

This patch release (v3.79.1) focuses heavily on bug fixes across the UI, Drizzle integration, and core validation logic. Performance improvements were also made to the Lexical rich text editor toolbar state management.

v3.79.0Breaking9 fixes3 features
Mar 4, 2026

This release introduces granular icon/thumbnail configuration for Lexical blocks and adds i18n support for modular dashboards. It also includes a significant upgrade to the underlying Lexical dependency and numerous bug fixes across plugins and the UI.

v3.78.06 fixes8 features
Feb 27, 2026

This release stabilizes the Trash feature and introduces significant enhancements to the UI, including editable query presets and configurable dashboard widgets. It also adds a powerful TypeScript plugin for component path validation.

v3.77.015 fixes4 features
Feb 18, 2026

This release introduces consistency for API depth across local and remote calls and adds support for custom IDs during document creation via `db.create`. It also includes numerous bug fixes across plugins like MCP, cloud-storage, and import-export, alongside updating the MCP plugin dependency.

v3.76.17 fixes
Feb 11, 2026

Patch release v3.76.1 addresses several bugs across the admin UI, file handling, and rich text editor, improving stability and security.

v3.76.08 fixes1 feature
Feb 9, 2026

This release introduces configurable limits for the import-export plugin and addresses several bugs across Drizzle, Next.js integration, and the UI components. It also drops support for vulnerable Next.js versions.

v3.75.013 fixes2 features
Feb 5, 2026

Version v3.75.0 introduces new component slots for navigation customization and improves context passing in Next.js server functions. Numerous bug fixes address issues across uploads, GraphQL, multi-tenancy, and UI rendering.

v3.74.0Breaking17 fixes6 features
Jan 30, 2026

This release introduces granular control over access in document hooks, extends TypeScript draft type checking across all local operations, and adds support for R2 multipart uploads. Numerous bug fixes address issues related to UI state, localization, and plugin behavior.

v3.73.0Breaking14 fixes7 features
Jan 23, 2026

This release introduces full support for Next.js 16 and enhances database flexibility with SQLite WAL mode and busy timeout options. It also includes numerous bug fixes across database drivers, UI components, and the SDK, alongside a migration helper for `blocksAsJSON`.

v3.72.013 fixes2 features
Jan 16, 2026

This release introduces experimental per-locale status localization and adds depth parameter support to MCP resource tools. It also includes numerous bug fixes across database operations, plugins, and UI rendering.

Common Errors

DrizzleQueryError6 reports

DrizzleQueryError in Payload CMS often arises from attempting to create enum types or tables that already exist in the database during migration. To fix this, carefully review your Drizzle schema and migration files, ensuring you're not creating duplicate enum types or tables. Employ conditional logic within your migrations to first check if the schema element exists before attempting to create it, or use `db.execute` to drop the existing enum/table before recreating it.

ValidationError5 reports

This error typically occurs in payload-cms. Check the example issues for common solutions.

APIError2 reports

This error typically occurs in payload-cms. Check the example issues for common solutions.

FileRetrievalError1 report

FileRetrievalError usually arises when Payload CMS can't access uploaded files due to incorrect `serverURL` or `staticDir` configurations. Ensure `serverURL` in your payload.config.ts is a fully qualified domain with protocol (http/https) and that it matches how your server is accessed, and verify `staticDir` points to the correct asset directory. Double-check file system permissions to allow Payload CMS read access of the asset directory.

MongoNetworkError1 report

MongoNetworkError often arises when Payload CMS can't resolve the MongoDB connection string's hostname, usually due to a typo, DNS issue, or the database not being publicly accessible. Double-check your `MONGODB_URI` environment variable for accuracy, ensure your database is reachable from the Payload CMS server (firewall rules, VPC peering), and confirm DNS resolution is functioning correctly in your hosting environment.

MongoServerError1 report

MongoServerError in Payload CMS usually arises from schema validation failures during database operations, like inserting or updating data that violates defined constraints. To fix this, carefully examine your Payload CMS collection schemas, ensuring that data types, required fields, and validation rules (like min/max values for numbers or regex patterns for strings) are correctly defined to match the data being entered. Adjust your schemas or sanitize/validate the incoming data before it hits the database to prevent these violations.

Related Backend & Infra Packages

Subscribe to Updates

Get notified when new versions are released

RSS Feed