Skip to content

fix: pin packaging to newest semver; do not fail on bump push - #19

Merged
xeaser merged 1 commit into
mainfrom
fix/packaging-bump-semver-and-push
Aug 24, 2026
Merged

fix: pin packaging to newest semver; do not fail on bump push#19
xeaser merged 1 commit into
mainfrom
fix/packaging-bump-semver-and-push

Conversation

@xeaser

Copy link
Copy Markdown
Owner

What

Backfilling v0.5.1 published the GitHub Release (good), then packaging-bump treated it as Latest (GitHub Latest = newest-created, not highest semver) and tried to pin Homebrew/Scoop/winget down to 0.5.1. The push 403'd (PACKAGING_BUMP_TOKEN cannot push), which failed the whole release job.

  • Compare git tag --sort=-v:refname; skip the pin when this tag is not the newest stable tag.
  • If the bump token cannot push, warn and exit 0 so the published release stays green.

v0.5.2 is marked Latest again. v0.5.1 remains a real release with assets.

How to test

  • go test ./internal/version
  • Docs (no change)

Checklist

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

GitHub Latest is the newest-created release, so backfilling v0.5.1
looked like latest and tried to downgrade pins. Compare git tags.
A 403 from PACKAGING_BUMP_TOKEN must not fail the release job.
@xeaser
xeaser merged commit 1f36a43 into mainAug 24, 2026
10 checks passed
@xeaser
xeaser deleted the fix/packaging-bump-semver-and-push branch August 24, 2026 13:10
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