Skip to content

Document Directus 12.6.0 - #855

Open
ChristopherJennings wants to merge 1 commit into
mainfrom
claude/release-notes-docs-sync-11230b
Open

ChristopherJennings wants to merge 1 commit into
mainfrom
claude/release-notes-docs-sync-11230b

Conversation

@ChristopherJennings

Copy link
Copy Markdown
Contributor

Summary

Documents Directus 12.6.0, released 2026-10-27.

Release pages

  • Breaking changes: new Version 12.6.0 section covering:
    • the Node.js 26 requirement and its effect on extensions
    • removed deprecated AI models, and recommended defaults for unset Allowed Models
    • the OpenAPI x-metadata → Metadata rename
    • the telemetry and compliance URL move to telemetry.directus.com
    • the PUBLIC_POLICY_ID removal from @directus/constants
  • Changelog: October 2026 now lists three releases, with a 12.6.0 summary.

Pages updated to match 12.6.0

Not included here

⚠️ Inferred, please verify

The following statements are my own inferences from code, specs, or Node.js itself. The 12.6.0 release notes and PRs don't state them directly.

  1. Node.js 26 doesn't bundle Corepack. This comes from Node.js dropping Corepack from its distribution in v25, not from Update to Node v26 directus#27737. That PR only says Directus stopped using Corepack. The breaking change entry and both Dockerfile examples rely on it: corepack enable → npm install --global pnpm. Please confirm that corepack enable really fails on node:26-alpine.
  2. RETENTION_BATCH cap values. The examples (999 on Oracle, 2097 on MS SQL Server) are worked out from getMaxBindings() - 1 in the retention schedule. Oracle returns 1000 and MS SQL Server returns 2098. SQLite (32765) and PostgreSQL (65534) aren't listed. MySQL has no cap.
  3. MCP clients carry on over POST after a 405. The troubleshooting entry says most clients continue automatically. This is based on the MCP Streamable HTTP spec, which allows servers to answer the optional GET stream with 405. Neither the PR nor I tested it against real clients.
  4. "Previously, new projects had no allowed models." This comes from a review note on Update built-in AI model lists and defaults directus#28344: the settings row was created after migrations ran, so fresh installs never got the default list. The release notes don't say it.
  5. Public role policies are found with role and user both null on directus_access. This comes from the app's new useIsAttachedToPublicRole composable in Show public permission notices for any policy within the public role directus#28348. The breaking change entry gives it as the replacement for PUBLIC_POLICY_ID.

Testing

Ran pnpm dev locally and checked that every changed page renders. All new internal links and anchors resolve, including #version-1260 from the changelog.

🤖 Generated with Claude Code

Add the Version 12.6.0 section to the v12 breaking changes page covering
the Node.js 26 requirement and its effect on extensions, the removed
deprecated AI models and recommended default allowed models, the OpenAPI
x-metadata rename to Metadata, the telemetry and compliance URL move to
telemetry.directus.com, and the PUBLIC_POLICY_ID removal from
@directus/constants.

Add 12.6.0 to the October 2026 changelog. Document recommended default
allowed models in the AI setup guide, license warnings in the sidebar,
the RETENTION_BATCH cap and validation, and the /mcp 405 response. Update
the Dockerfile examples to node:26-alpine and replace corepack enable,
note the Node.js 26 requirement for npm installs, and replace the
Corepack advice in the contributor setup guide.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
docs Ready Ready Preview Oct 28, 2026 9:07pm UTC

Request Review

This branch was successfully deployed

1 active deployment
Preview — 4a61399e Deployed Oct 28, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant