Problem

20+ failed release builds since the monorepo consolidation (Feb 2) have left stale tags and misnamed releases on GitHub. These need cleanup after #82 and #83 are fixed.

What needs cleanup

Stale v* temp tags (leaked by GoReleaser)

These were supposed to be local-only temp tags, but GoReleaser pushed them to the remote:

v0.1.100  v0.1.103  v0.1.14  v0.2.0  v0.9.100  v0.9.103  v0.9.13

Misnamed releases (created under v* instead of {tool}-v*)

All existing releases are under the wrong tag names:

Orphaned {tool}-v* tags (auto-release created tags but GoReleaser failed)

These tags exist but have no corresponding release:

jtk-v0.1.15  jtk-v0.1.16  jtk-v0.1.100  jtk-v0.1.101  jtk-v0.1.102
cfl-v0.9.100  cfl-v0.9.101  cfl-v0.9.102

Cleanup steps

# 1. Delete misnamed releases
for tag in v0.1.100 v0.1.103 v0.1.14 v0.2.0 v0.9.100 v0.9.103 v0.9.13; do
  gh release delete "$tag" --yes
done

# 2. Delete stale v* temp tags
for tag in v0.1.100 v0.1.103 v0.1.14 v0.2.0 v0.9.100 v0.9.103 v0.9.13; do
  git push origin ":refs/tags/$tag"
done

# 3. Delete orphaned {tool}-v* tags that never got a release
for tag in jtk-v0.1.15 jtk-v0.1.16 jtk-v0.1.100 jtk-v0.1.101 jtk-v0.1.102 cfl-v0.9.100 cfl-v0.9.101 cfl-v0.9.102; do
  git push origin ":refs/tags/$tag"
done

# 4. Clean up local tags
git fetch --prune origin "+refs/tags/*:refs/tags/*"

Depends on

• fix: Remove GoReleaser Pro-only alternative_names from jtk cask config #82 and fix: Release tag mismatch — chocolatey/winget can't find GoReleaser releases #83 must be merged first — otherwise the next release will just create more stale artifacts