Skip to content

Prepare v1.4.3 release - #30

Merged
Reedtrullz merged 1 commit into
mainfrom
codex/v1.4.3-release-prep
Aug 8, 2026
Merged

Prepare v1.4.3 release#30
Reedtrullz merged 1 commit into
mainfrom
codex/v1.4.3-release-prep

Conversation

@Reedtrullz

Copy link
Copy Markdown
Owner

The release-prep gate requires the prep commit to be the final commit on main with the candidate version advancing and only the four release files changing. The v1.4.2 prep merged before the hardening PR, and the manifest continuity gate forbids moving the candidate backward, so v1.4.2 is superseded before publication; this PR advances the candidate to v1.4.3 build 11 carrying the identical source changes.

Changes (only the four release files)

  • .github/release-manifest.json: candidate 1.4.3 / build 11 / v1.4.3 artifact names.
  • Resources/Info.plist: 1.4.3 / build 11.
  • CHANGELOG.md: 1.4.3 entry (containment fix, diagnostics consolidation, agent-control hardening, CI timeout) + scope note for the v1.4.2 supersession.
  • docs/release-status.md: candidate references advanced; v1.4.2 supersession documented.

Verification

  • check-release-manifest.sh: OK (candidate v1.4.3).
  • validate-release-metadata.sh --mode developer-id: OK (1.4.3 / Vifty-v1.4.3.zip).
  • render-release-facts.sh --check: OK. git diff --check: clean.

Non-claims

  • No tag, push, or release mutation. Merging this PR last makes main a valid signed-release-tag target.

The release-prep gate requires the prep commit to be the final commit on main
with the candidate version advancing. The v1.4.2 prep merged before the
hardening PR and the manifest continuity gate forbids moving the candidate
backward, so v1.4.2 is superseded before publication and the release advances
to v1.4.3 build 11 carrying the identical source changes.
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@Reedtrullz
Reedtrullz merged commit 8df7ad7 into main Aug 8, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant