Skip to content

fix: align release-docs budget to published 4.x anchor - #116

Merged
CruxExperts merged 7 commits into
mainfrom
fix/anchor-4.44.1-qc-timeouts
Sep 26, 2026
Merged

CruxExperts merged 7 commits into
mainfrom
fix/anchor-4.44.1-qc-timeouts

Conversation

@CruxExperts

Copy link
Copy Markdown
Owner

Summary

  • Use the verified published v4.44.1 commit as the 4.x arithmetic baseline while preserving published v5.6.2 and v4.22.9 release assets.
  • Set release-docs preparation defaults to 800 calls and a 9,000-second (150-minute) whole-session budget. Keep the per-request timeout separate and allow a 15-minute validation grace period in the 165-minute hosted job.
  • Add the 4.44.2 release record and guide, correct timeout and historical version wording, and refresh generated documentation receipts.

Version plan

  • Canonical planning maps the maintenance fix from v4.44.1 to v4.44.2 as one PATCH slice. The major line remains locked to 4.x.
  • Preserve the existing SDK paging and Agent Q v2/envelope compatibility disclosures.

Validation

  • Focused release-docs tests: 24 passed.
  • release-docs check --version 4.44.2 --verify-baseline: zero findings.
  • Docs-alignment CI check: zero findings.
  • validate-catalog and validate-package-surface: no issues.
  • Both documentation generators rerun after the receipt commit without drift.
  • publish-preflight --base origin/main --head HEAD: passed with no prepared changes.
  • git diff --check: passed.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 25, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-25T22:15:43.735520Z 6b2f03d PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@github-actions github-actions Bot added area/docs Affected repository area area/release Affected repository area status/needs-triage Triage status type/pr Issue or PR type labels Sep 25, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

@CruxExperts
CruxExperts merged commit 6b2f03d into main Sep 26, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/docs Affected repository area area/release Affected repository area status/needs-triage Triage status type/pr Issue or PR type

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant