Skip to content

fix: restore LocalSetup to the 4.x release line - #115

Merged
CruxExperts merged 3 commits into
mainfrom
fix/4x-release-line
Sep 25, 2026
Merged

CruxExperts merged 3 commits into
mainfrom
fix/4x-release-line

Conversation

@CruxExperts

Copy link
Copy Markdown
Owner

This PR corrects LocalSetup's release numbering to 4.44.1 and locks future release arithmetic to the 4.x line.

  • Reconciles accepted history through 4.43.2, maps the branding slice to 4.44.0 and the repository naming slice to 4.44.1, and preserves the published v5.6.2 and v4.22.9 releases and tags.
  • Removes the unpublished 5.7.0 and 5.7.1 draft records. GitHub has no tags or releases for those versions.
  • Adds corrected 4.44.1 release notes, including the existing SDK paging and Agent Q v2/signed-envelope compatibility warnings. Renumbering does not restore compatibility.
  • Makes the installer fallback avoid choosing a numerically higher tag from a different major line when the release API is unavailable.

Validation:

  • version-plan --base origin/main --head HEAD: passed; target 4.44.1, major line 4, no major-line violations, historical sync checks valid.
  • release-docs check --version 4.44.1: passed with no findings.
  • publish-preflight --base origin/main --head HEAD: passed with no prepared changes.
  • Focused version, release-document, installer, documentation-alignment, branding, and graphics-render checks are recorded in the maintenance ledger. The local broader suite encounters an ignored broken adapter-symlink fixture; full CI is the required suite gate for merge.
  • All three commits are signed with the repository's required OpenPGP key; git diff --check passes.

@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-25T16:15:42.636030Z 561abef 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/installer Installer, bootstrap, conversion, or rollback 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: 561abefe0a

ℹ️ 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".

Comment on lines +115 to +119
published_anchor = version_plan.get("published_anchor")
if (isinstance(published_anchor, dict)
and isinstance(version_plan.get("line_reconciliation"), dict)):
source_base = str(published_anchor["commit"])
baseline_tag = str(published_anchor["tag"])

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Preserve the v5.6.2 baseline in repair mode

When v4.44.1 has been published and release-docs ... --repair --verify-baseline is used, control enters the repair branch before this new reconciliation-aware anchor handling. _prior_release() compares versions numerically, so it excludes v5.6.2 because it is greater than 4.44.1 and can select v4.22.9 instead; the repair candidate then includes the entire already-published migration history and may rewrite the 4.44.1 notes from the wrong baseline. Apply the reconciliation/published-anchor selection to repair planning as well.

AGENTS.md reference: AGENTS.md:L55-L62

Useful? React with 👍 / 👎.

@CruxExperts
CruxExperts merged commit 561abef into main Sep 25, 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/installer Installer, bootstrap, conversion, or rollback 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