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

Merged

Claude merged 1 commit from 0.2.0/fix-ref-name-trim-tags-prefix into main

2026-06-22 13:39:16 +00:00

Claude commented

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

Member

Summary

windows-release.yml's PowerShell branch/isMain resolution was silently falling through to the dev/prerelease naming path for every tag-dispatched build, confirmed by a live run publishing dev-v0.1.39 instead of v0.1.39 despite the ref-matching fix from #130.
Trim github.sha/github.ref_name and strip a refs/tags/ prefix in addition to refs/heads/ before the $isMain regex check.
Mirrored the refs/tags/ stripping in linux-appimage.yml for consistency (its bash equivalent was working correctly, but the same defensive trim is cheap insurance).

Why

Following up on #130: that PR added vX.Y.Z-tag-dispatch as a canonical-release path, and it works correctly for linux-appimage.yml, but windows-release.yml kept publishing under dev-{branch} naming for every tag dispatch, blocking the historical-release backfill for several 0.1.x versions' Windows artifact.

Test plan

YAML validity checked locally.
After merge: dispatch windows-release.yml against an existing tag and confirm it publishes to the canonical vX.Y.Z release, not dev-vX.Y.Z.

## Summary - `windows-release.yml`'s PowerShell branch/`isMain` resolution was silently falling through to the dev/prerelease naming path for every tag-dispatched build, confirmed by a live run publishing `dev-v0.1.39` instead of `v0.1.39` despite the ref-matching fix from #130. - Trim `github.sha`/`github.ref_name` and strip a `refs/tags/` prefix in addition to `refs/heads/` before the `$isMain` regex check. - Mirrored the `refs/tags/` stripping in `linux-appimage.yml` for consistency (its bash equivalent was working correctly, but the same defensive trim is cheap insurance). ## Why Following up on #130: that PR added `vX.Y.Z`-tag-dispatch as a canonical-release path, and it works correctly for `linux-appimage.yml`, but `windows-release.yml` kept publishing under `dev-{branch}` naming for every tag dispatch, blocking the historical-release backfill for several 0.1.x versions' Windows artifact. ## Test plan - [x] YAML validity checked locally. - [ ] After merge: dispatch `windows-release.yml` against an existing tag and confirm it publishes to the canonical `vX.Y.Z` release, not `dev-vX.Y.Z`.

Claude added 1 commit

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

ci: harden tag-ref detection for workflow_dispatch canonical releases

CI / lint (push) Successful in 7s

Details

CI / test (push) Successful in 1m29s

Details

CI / appimage (push) Successful in 7m51s

Details

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

Details

CI / windows-exe (push) Successful in 11m16s

Details

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

Details

bff5d662b6

windows-release.yml's PowerShell branch/isMain resolution was silently
falling through to the dev/prerelease path for every tag-dispatched
build (confirmed via dev-v0.1.39 being published instead of v0.1.39) -
trim github.sha/ref_name and strip a refs/tags/ prefix in addition to
refs/heads/. Mirror the refs/tags/ stripping in linux-appimage.yml for
consistency, even though its bash equivalent was working correctly.

Claude merged commit 6bd5e2898f into main

2026-06-22 13:39:16 +00:00

Claude referenced this pull request from a commit

2026-06-22 13:39:17 +00:00

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

No reviewers

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

ai-collab/bulk-image-organizer!132

No description provided.

Rows
Columns