Repository navigation
ci(install): check the install paths after every release - #153
Merged
Merged
Conversation
The release workflow publishes the release with its own token, so `release: published` never fires for it. The install workflow now also runs when a Release run completes; it goes on only after a successful run started by a tag push, so dry runs from pull requests and failed releases start nothing. Every job needs `latest`, which carries the condition. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RzKPspjwDD5zGUL5Vyxphv
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The install workflow (#148) listens to
release: published, but the release workflow publishes with its ownGITHUB_TOKEN, and events created by that token start no workflow. So after a normal release only the weekly run checked the new version.It now also runs on
workflow_runofRelease(types: [completed]). Thelatestjob, which every other job needs, goes on only when that run succeeded and was started by a push (a tag): pull-request dry runs and failed releases start nothing. A Release run finishes only after the publish jobs, so the channels are up to date except npm (waiting for a maintainer's approval) and Homebrew withoutHOMEBREW_TAP_TOKEN, as the header comment says.actionlint(withshellcheck) is clean.🤖 Generated with Claude Code
https://claude.ai/code/session_01RzKPspjwDD5zGUL5Vyxphv