Add crates.io and npm publish workflows - #17
Merged
Conversation
Introduce reusable publish-crates and publish-npm workflows that can be triggered manually or from the release workflow on version tags. - Enable chorus-relay for crates.io with readme and metadata - Mark @chorus/shared, @chorus/client, and @chorus/plugin as public npm packages (OpenCode plugin plus its workspace dependencies) - Add scripts/publish-npm.sh for ordered npm publish with dry-run and skip-if-already-published behavior - Wire release.yml to publish after CI passes on v* tags Co-authored-by: Steven Roomberg <sroomberg@users.noreply.github.com>
sroomberg
marked this pull request as ready for review
August 31, 2026 14:21
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
2 participants
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
Adds reusable GitHub Actions workflows to publish chorus-relay to crates.io and the OpenCode npm packages (
@chorus/shared,@chorus/client,@chorus/plugin) to npm. Both workflows can be run on their own or are invoked automatically by the existing release workflow when av*tag is pushed.Workflows
workflow_dispatch) or called from Releasechorus-relayworkflow_dispatch) or called from Release@chorus/shared,@chorus/client,@chorus/pluginv*tagEach publish workflow supports:
Package metadata
publish = falsefromchorus-relayand added crates.io metadata (readme, keywords, categories)private: truefrom the three npm packages that ship with the OpenCode plugin; addedpublishConfig.access: public@chorus/sharedversion to2.1.0to match the other packagesSecrets required
Configure these repository secrets (or trusted publishing equivalents):
CARGO_REGISTRY_TOKEN— crates.io API tokenNPM_TOKEN— npm automation token with publish access to@chorus/*Manual usage
2.1.0) to verify manifests before publishRelease usage
Push a tag whose version matches the manifests (e.g.
v2.1.0whenCargo.tomlandpackage.jsonare2.1.0). CI runs first; then GitHub release creation and both registry publishes run in parallel.