ci: treat vX.Y.Z tag dispatch as a canonical release #130

Merged

Claude merged 1 commit from 0.2.0/release-tag-dispatch-canonical into main

2026-06-22 04:24:11 +00:00

Claude commented

2026-06-22 04:15:26 +00:00

Member

Summary

workflow_dispatch triggered against a version tag (e.g. v0.1.5) now resolves the same way a push to main does: canonical vX.Y.Z release naming, prerelease=false.
make_latest stays false in the tag-dispatch case so main remains the only release ever marked "latest".
Workflow-only change; no VERSION bump per AGENTS.md (confirmed via ./scripts/check-version-bump.sh origin/main).

Why

Needed to backfill historical 0.1.x releases with both Linux .AppImage and Windows .exe artifacts without rewriting main's history. Pushing a tag triggers nothing (ci.yml only listens to branch pushes), and dispatching against any non-main ref previously always produced a dev-* prerelease regardless of the checked-out VERSION file. This lets us dispatch against a tag pointing at the exact historical main commit for each version and get a correctly-named canonical release.

Test plan

python3 -c "import yaml; yaml.safe_load(...)" on both edited workflow files — valid YAML.
./scripts/check-version-bump.sh origin/main — confirms no bump required.
After merge: dispatch linux-appimage.yml against an existing tag (e.g. v0.1.30) and confirm it updates release v0.1.30 (not a dev-v0.1.30 prerelease) with make_latest unset.

## Summary - `workflow_dispatch` triggered against a version tag (e.g. `v0.1.5`) now resolves the same way a push to `main` does: canonical `vX.Y.Z` release naming, `prerelease=false`. - `make_latest` stays `false` in the tag-dispatch case so `main` remains the only release ever marked "latest". - Workflow-only change; no `VERSION` bump per `AGENTS.md` (confirmed via `./scripts/check-version-bump.sh origin/main`). ## Why Needed to backfill historical 0.1.x releases with both Linux `.AppImage` and Windows `.exe` artifacts without rewriting `main`'s history. Pushing a tag triggers nothing (`ci.yml` only listens to branch pushes), and dispatching against any non-`main` ref previously always produced a `dev-*` prerelease regardless of the checked-out `VERSION` file. This lets us dispatch against a tag pointing at the exact historical `main` commit for each version and get a correctly-named canonical release. ## Test plan - [x] `python3 -c "import yaml; yaml.safe_load(...)"` on both edited workflow files — valid YAML. - [x] `./scripts/check-version-bump.sh origin/main` — confirms no bump required. - [ ] After merge: dispatch `linux-appimage.yml` against an existing tag (e.g. `v0.1.30`) and confirm it updates release `v0.1.30` (not a `dev-v0.1.30` prerelease) with `make_latest` unset.

Claude added 1 commit

2026-06-22 04:15:26 +00:00

ci: treat vX.Y.Z tag dispatch as a canonical release

CI / lint (push) Successful in 7s

Details

CI / test (push) Successful in 1m52s

Details

CI / appimage (push) Successful in 8m30s

Details

CI / build-appimage (push) Successful in 0s

Details

CI / windows-exe (push) Successful in 9m23s

Details

CI / build-windows-exe (push) Successful in 0s

Details

847c7776f6

workflow_dispatch against a version tag (e.g. v0.1.5) now resolves the
same way a push to main does — canonical release-tag naming and
prerelease=false — instead of always falling into the dev/prerelease
branch path. make_latest stays false for the tag-dispatch case so main
keeps being the one "latest" release. Needed to backfill historical
0.1.x releases with both platform artifacts without rewriting main's
history.

Claude merged commit c4d794a079 into main

2026-06-22 04:24:11 +00:00

Claude referenced this pull request from a commit

2026-06-22 04:24:13 +00:00

ci: treat vX.Y.Z tag dispatch as a canonical release (#130)

Claude referenced this pull request

2026-06-22 13:28:58 +00:00

ci: harden tag-ref detection for workflow_dispatch canonical releases #132