Repository navigation
Recover skipped container publication from verified release tags - #88
Merged
Merged
Conversation
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
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.
The v0.2.49 release assets are published, but its container job was skipped after the release job exceeded GitHub's release-body limit. Rerunning that job kept it skipped. This adds a separate manual container-only workflow without repeating verification or changing the release tag.
The workflow runs only from the default branch. It requires a stable release tag and reviewed full commit SHA, verifies an existing public, published, non-draft release, resolves annotated or lightweight tags, and checks the tagged Forge version. It preserves its guard outside the build context, checks out the resolved SHA with credentials disabled, then rechecks release/tag identity and the clean checkout immediately before the existing pinned GHCR build/push steps. OCI revision/version labels use the validated source; provenance and SBOM remain enabled.
Validation: 28 focused release/workflow tests pass, including nine new guard/contract tests; strict mypy, Ruff, formatting, and diff checks pass. Read-only GitHub checks independently bound the actual v0.2.49 release to 0225325 and revalidated the unchanged release/tag identity against a clean exact-tag checkout.
No image build, workflow dispatch, tag change, release publication, or runtime deployment was performed by this change. Hosted CI and the actual recovery dispatch/image verification remain pending.
After merge, the release owner can run: