Skip to content

Publish qualified releases when artifacts are reused - #51

Merged
stepandel merged 1 commit into
mainfrom
codex/fix-prepared-release-publish
Oct 23, 2026
Merged

stepandel merged 1 commit into
mainfrom
codex/fix-prepared-release-publish

Conversation

@stepandel

Copy link
Copy Markdown
Owner

When a release tag reuses already qualified native artifacts, its matrix jobs are skipped. GitHub's implicit success() check then skips publication through those ancestors even though prepared and qualified succeeded. The 0.3.4 tag run reproduced this and required publishing its verified archives through the equivalent release commands.

Use an explicit cancellation/status guard so a push of a qualified tag publishes with either fresh or reused artifacts. Require both prerequisite jobs to succeed and retain the tag-only restriction.

Validation: all release-tooling tests passed. The observed tag run and qualified archives are https://github.com/stepandel/juiced/actions/runs/40030376505.

@vercel

vercel Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
juiced Ready Ready Preview Oct 23, 2026 10:01pm UTC

Request Review

@stepandel
stepandel merged commit 5b243c9 into main Oct 23, 2026
4 checks passed
@stepandel
stepandel deleted the codex/fix-prepared-release-publish branch October 26, 2026 15:25
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