fix: align release-docs budget to published 4.x anchor - #116
Conversation
Release-Type: patch
Release-Type: none
Release-Type: none
Release-Type: none
Release-Type: none
Release-Type: none
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6b2f03d7fd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| { | ||
| "schema_version": 1, | ||
| "version": "4.44.2", | ||
| "source_commit": "9839e6f0ae1563395609dfae6dea315574988634", |
There was a problem hiding this comment.
Preserve an ancestral source snapshot for release docs
When this squashed commit is checked out, the new record names 9839e6f0ae1563395609dfae6dea315574988634, but git merge-base --is-ancestor 9839e6f... 0ff08a5... exits 1; generated receipts likewise reference ac1e60d... from the discarded commit chain. Consequently, the mandatory release-docs check emits source_not_ancestor in both preparation and publication, blocking v4.44.2. Preserve the source/docs commit chain or rebuild the release record and generated receipts around a source commit that is actually ancestral to the final candidate.
AGENTS.md reference: AGENTS.md:L146-L154
Useful? React with 👍 / 👎.
Summary
Version plan
Validation
release-docs check --version 4.44.2 --verify-baseline: zero findings.validate-catalogandvalidate-package-surface: no issues.publish-preflight --base origin/main --head HEAD: passed with no prepared changes.git diff --check: passed.