Prepare v1.4.2 release and record v1.4.1 retirement - #27
Merged
Conversation
Advance the release candidate to 1.4.2 build 10 after the v1.4.1 one-shot transaction failed at the publish step and its tag is durably retired without publication. Document the exact retired tag object, commit, first-attempt run, and failure mode in release-status.md, and add the 1.4.2 changelog entry.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
1 participant
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.
Part 3 of the 2026-08-07 deep-review remediation.
Changes
1.4.2build10in.github/release-manifest.jsonandResources/Info.plist(artifact names follow the manifest).v1.4.1retirement indocs/release-status.md: immutable tag object04341420…at commitdfc68ac…, first-attempt run29668876169failed at the publish step, no GitHub Release exists (by-tag 404), tag must not be reused/rerun; recovery advances to v1.4.2.Verification
check-release-manifest.sh: OK (candidate v1.4.2).validate-release-metadata.sh --mode developer-id: OK (1.4.2 / Vifty-v1.4.2.zip).render-release-facts.sh --check: OK.git diff --check: clean.Non-claims