Skip to content

Start the tap update when a release is published - #20

Merged
nnutter merged 2 commits into
masterfrom
update-tap
Nov 5, 2026
Merged

nnutter merged 2 commits into
masterfrom
update-tap

Conversation

@nnutter

@nnutter nnutter commented Nov 5, 2026

Copy link
Copy Markdown
Owner

No description provided.

A workflow run that GITHUB_TOKEN starts starts no further run, so a
release that GITHUB_TOKEN publishes cannot start the tap update. The app
token publishes the release instead, and it starts the tap update, which
is how timber already publishes.

The release.yaml files were otherwise the same as timber's, so the token
step and the publish step now match it.

Change-Id: I0772d12cf71a9b0b0f98ab6eb4a2d55c140d6939
The push of a version tag fires before the release exists, so the
workflow asked GitHub for a release that was not there yet and stopped
with HTTP 404. constable v0.5.2, constable v0.6.0, git-bump v0.3.4, and
roam v2.1.3 all left a stale formula that way. Listening for the
published release removes the race, because the release and its assets
exist by then.

The tag branch of the resolve step goes with the trigger, so the step
takes only the release tag or the dispatch input, as timber's step does.

Change-Id: I4488835faea75bb2e7e60de05b34d70379febfb2
@nnutter
nnutter merged commit d015dec into master Nov 5, 2026
3 checks passed
@nnutter
nnutter deleted the update-tap branch November 5, 2026 07:11
Sign up for free to 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