Repository navigation
docs: prepare v0.5.79 release notes - #4572
Closed
yannickmonney wants to merge 4 commits into
Closed
yannickmonney wants to merge 4 commits into
yannickmonney wants to merge 4 commits into
Conversation
Contributor
Author
|
The reviewed v0.5.79 notes were incorporated and updated in #4565, merged as |
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
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.
Prepare v0.5.79 forward-release notes for API-key expiry controls, chat attachment access, erasure receipts, automation parsing, private deployment-control routing, compact task occupancy reads, sandbox overhead and cleanup, knowledge vector widths, safe CLI Git diagnostics, and the managed automation cutover barrier. Explain the stopped v0.5.78 publication and the required migration, compatibility and rollout steps.
This remains a draft. Landing requires the final #4565 composition, including #4569 and #4573, and the reviewed #4579 managed cutover to reach main, followed by reconciliation against that exact source. The child PR links remain provenance for their changes. These notes do not establish a completed release or deployment. Candidate selection, tagging and rollout still require their maintained gates and a safe protocol cutover.
Validation: maintained release-note validator and diff check passed. Markdown is excluded by repository formatting configuration; the stdin formatter returned the final text unchanged, and normal commit hooks passed. Independent factual review and root review accepted the final prose. The complete local Markdown page was inspected through T3 preview at 1280px and 390px, with correct section order, links and no narrow horizontal overflow. This is documentation verification, not deployed-product verification. Exact-head PR CI and final source reconciliation remain pending.