fix: combine release-please and publish into single workflow#7
Merged
Conversation
The separate release-please.yml created tags via GITHUB_TOKEN, which does not trigger downstream on-tag workflows (GitHub Actions limitation). This meant release.yml never ran for v0.2.2 or v0.3.0, so npm publish never happened. Merge both into release.yml following the openclaw-plugin pattern: release-please runs first, then publish gates on releases_created output. Also adds workflow_dispatch to manually trigger publishes. Co-Authored-By: Claude Opus 4.6 (1M context) <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.
Summary
The release pipeline was broken:
release-please.ymlcreated GitHub Releases and tags usingGITHUB_TOKEN, but GitHub Actions does not triggeron: push: tagsworkflows fromGITHUB_TOKEN-created events (to prevent infinite loops). This meantrelease.yml(npm publish) never ran — v0.2.2 and v0.3.0 were never published to npm.Combines both workflows into a single
release.ymlfollowing the pattern used inopenclaw-plugin:release-pleasejob runs on push to main, outputsreleases_createdpublishjob gates on that output and runs npm publishworkflow_dispatchallows manual publish (useful for recovering v0.3.0)Type
Changes
.github/workflows/release.yml: merged release-please + publish into single workflow.github/workflows/release-please.yml: deleted (redundant)Checklist
QA Instructions
workflow_dispatchon the Release workflow to publish v0.3.0npm view @eterna-hybrid-exchange/cli versionsincludes 0.3.0