public/soundy-bits
1
0
Fork 0
Code Issues Pull requests Projects Releases 5 Packages Wiki Activity Actions

fix(ci): one tag push so release.yml runs exactly once #14

Merged
psk merged 1 commit from fix/release-single-tag into master 2026-06-28 19:10:28 +00:00
Conversation 0 Commits 1 Files changed 2 +23 -27
psk commented 2026-06-28 18:54:36 +00:00
Owner
Copy link

Fixes release.yml firing TWICE per release.

Root cause (verified via the Actions API): release-plz.yml pushed the tag via two mechanisms — release-plz release (its own tag push) AND a separate re-push step. Once PR #13 made both use the RELEASE_TOKEN PAT, both fired release.yml -> two runs for v0.3.1 on the same commit 5424d626.

Fix: replace both steps with a single explicit PAT git push of the tag (guarded to only fire when masters version is untagged = a Release-PR merge). Drop release-plz release. One push = one release run. Mirrors the bossman release-tag pattern. No change to release.yml.

Fixes release.yml firing TWICE per release. Root cause (verified via the Actions API): release-plz.yml pushed the tag via two mechanisms — release-plz release (its own tag push) AND a separate re-push step. Once PR #13 made both use the RELEASE_TOKEN PAT, both fired release.yml -> two runs for v0.3.1 on the same commit 5424d626. Fix: replace both steps with a single explicit PAT git push of the tag (guarded to only fire when masters version is untagged = a Release-PR merge). Drop release-plz release. One push = one release run. Mirrors the bossman release-tag pattern. No change to release.yml.
fix(ci): push the release tag once so release.yml runs once
All checks were successful
ci / build-and-test (pull_request) Successful in 9m41s
Details
fa50351d6f
 
release-plz.yml pushed the vX.Y.Z tag via TWO mechanisms — `release-plz
release` (its own tag push) plus a separate explicit re-push — and once
both authenticated with the RELEASE_TOKEN PAT, both fired release.yml, so
every release built twice (verified: two release.yml runs for v0.3.1 on
the same commit 5424d626).

Replace both steps with a single explicit PAT `git push` of the tag,
guarded so it only fires when master's version isn't tagged yet (i.e. a
Release-PR merge). Drop `release-plz release` (with publish=false +
git_release_enable=false it only created/pushed the tag). One push = one
release run. Mirrors the proven bossman release-tag pattern.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
psk merged commit 0aef455fde into master 2026-06-28 19:10:28 +00:00
psk deleted branch fix/release-single-tag 2026-06-28 19:10:28 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
public/soundy-bits!14
No description provided.