Repository navigation
release-notes-describe-the-product - #941
Merged
Merged
Conversation
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.
Codex CLI and ACP support was recorded only in Core's changelog. Product users saw
Updated dependencies, GitHub releases led with a PR list, and wrapped summaries lost their continuation lines in the website manifest.This change announces the existing Codex capability in Extension, Standalone and CLI notes: Harness stages, GPT model/effort, sandbox, output/file changes and tokens, including the separate ACP bridge requirement. It corrects historical copy without changing version headings, references or artifacts and adds a patch changeset for all three public deliveries.
OpenSpec now requires a short, concrete Changelog section and product-facing Changesets entries. ADR 0054 and the contributor guide define the product audience and an 80-word body limit. Checks reject empty/placeholder/overlong summaries; factual accuracy remains a review responsibility. Version PRs require authored public-product notes, and releases generate complete Highlights before tagging, followed by GitHub's generated history. Core remains internal and the manifest schema is unchanged.
Existing GitHub releases 0.106.3 and 0.106.4 already received authored Highlights. Readbacks confirmed each original body remains an exact suffix, with publication dates, tag objects and asset metadata unchanged. Version 0.106.4 explicitly dates Codex support to 0.106.3.
Validation: 48 targeted tests across changeset, release-note, OpenSpec-config, release-manifest and selected workflow tests; CLI TypeScript; ESLint on six changed source/test paths; scoped language/control-byte/budget/whitespace checks; real generator/check mode; Changesets status; actual OpenSpec instructions and strict change validation. Full verification runs only in CI.