Rewrite release-2026-05 breaking changes & deprecations in AI-parsable format#1162
Open
ajwild wants to merge 1 commit into
Open
Rewrite release-2026-05 breaking changes & deprecations in AI-parsable format#1162ajwild wants to merge 1 commit into
ajwild wants to merge 1 commit into
Conversation
…arsable format Apply the TRN format to the Breaking Changes and Deprecations sections: - Detect/Fix sub-sections with greppable Detect lines (literal tokens, not abstract dot-paths) and before/after tables for path renames - **Code:** lines linking entries to their LivingdocsBreakingChange / LivingdocsDeprecation log codes (verbatim from the server source) - Icon-free entry headings; add⚠️ to the Deprecations section heading - Move publicApi.executeDocumentCommands() from Features to Deprecations (opt-in default-behaviour change) - Redis: correct removal to release-2026-09 (first announced release-2026-03), per LIDEP079 - Fix the reserved dashboard handle casing to imageCollections Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jun 17, 2026
dfreier
reviewed
Jun 18, 2026
|
|
||
| - `mediaLibrary.images.processing.maxFileSize` → `mediaLibrary.images.uploadRestrictions.maxFileSize` | ||
| - `mediaLibrary.images.uploadRestrictions.maxResolution` → `mediaLibrary.images.processing.maxResolution` | ||
| **Codes:** `LIBREAKING064-failOn`, `LIBREAKING064-convert`, `LIBREAKING064-lossy`, `LIBREAKING064-lossless` |
dfreier
approved these changes
Jun 18, 2026
dfreier
left a comment
dfreier
left a comment
Contributor
There was a problem hiding this comment.
Fantastic! 🥳
What shall be the next steps to get CSO on board with this? Is something planned from E&S side?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Applies the AI-parsable TRN format to the Breaking Changes and Deprecations sections of
release-2026-05, so an AI agent (or operator) can parse them into a concrete upgrade checklist.Changes
Detect/Fixcontract, with icon-free entry headings.Detectlines — a literal token to search for (not an abstract dot-path), plus before/after tables for the path-rename entries.**Code:**lines linking each entry to itsLivingdocsBreakingChange/LivingdocsDeprecationlog code, taken verbatim from the server source. Entries with no runtime code (directlib/imports, usage-logparamsSchema) correctly omit it.## Deprecationsheading gains:warning:.publicApi.executeDocumentCommands()moved from Features → Deprecations (it's an opt-in default-behaviour change, not a feature).release-2026-09(first announcedrelease-2026-03), perLIDEP079.imageCollectionsto match the server.Notes
fix()so semantic-release triggers a patch/deployment on merge.🤖 Generated with Claude Code