Skip to content

fix: retry the same unpublished tag; do not skip versions - #17

Merged
xeaser merged 1 commit into
mainfrom
fix/release-no-skip-unpublished
Aug 24, 2026
Merged

fix: retry the same unpublished tag; do not skip versions#17
xeaser merged 1 commit into
mainfrom
fix/release-no-skip-unpublished

Conversation

@xeaser

Copy link
Copy Markdown
Owner

What

v0.5.1 was tagged but never got a GitHub Release; we jumped to v0.5.2. The v0.5.2 GoReleaser job published assets, then failed pushing Homebrew/Scoop/winget to main, so the packaging PR never opened. Auto-merge is also disabled on this repo, so gh pr merge --auto would fail that job even after a PR exists.

  • Refuse to publish a newer stable tag while the previous stable tag has no GitHub Release.
  • workflow_dispatch retries the same tag: checkout tag code, use origin/main:.goreleaser.yaml.
  • Packaging bump warns if auto-merge is unavailable (PR stays open).
  • Packaging bump skips when the tag is not the latest GitHub Release (backfilling 0.5.1 must not downgrade pins).

After merge: run Actions → release → v0.5.1 to publish the missing release.

How to test

  • go test ./...
  • Docs updated (CONTRIBUTING release section)

Checklist

  • Commits are signed
  • No secrets
  • Does not add Copilot, Ink shell, Aspire, or npm install

Refuse a newer stable tag while the previous one has no GitHub Release.
Retry via workflow_dispatch using main's GoReleaser config. Packaging
bump warns if auto-merge is off and skips pins for older backfills.
@xeaser
xeaser merged commit 518aab0 into mainAug 24, 2026
10 checks passed
@xeaser
xeaser deleted the fix/release-no-skip-unpublished branch August 24, 2026 12:57
Sign up for freeto 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

@xeaser