Repository navigation
ci: move the release workflow to homebridge/.github - #38
Merged
Merged
Conversation
Use the shared determine-npm-release workflow, which fails on any event and branch it does not recognise, so publish is skipped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
release.yml now only holds the triggers, permissions and concurrency, and calls the shared npm-release workflow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
NorthernMan54
changed the title
A cancelled run could leave a version on npm with no pre-release. New pushes now wait for the running release to finish. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Why
This run, started manually on
latest, reachednpm publish --tag none. It only failed because 2.2.6 was already published.What
release.ymlnow holds only its triggers, permissions and concurrency, and calls the sharednpm-release.yml, which fails on anything other than a release or abeta-*/alpha-*branch.Merge order
Merge after homebridge/.github#59. This calls the shared workflow at
@latest, so it breaks until that PR is in.Notes
cancel-in-progressis nowfalse, so a new push can't cancel a run after npm publish and leave a version with no pre-release.release.yml, so no npm change should be needed.latestafter the merge to pick this up.Testing
Not run on GitHub Actions yet. After both PRs merge, a manual run on
latestshould fail at the first job with nothing published. The nextbeta-*push is the first real test of publishing through the shared workflow, so check that one closely.🤖 Generated with Claude Code