chore(ci): add release and promote GitHub workflows#954
Merged
Conversation
Release workflow triggers on v* tag push — builds, publishes to npm next channel, and creates a GitHub release. Promote workflow is manual dispatch to move a version from next to latest dist-tag. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Deploying agentv with
|
| Latest commit: |
fbb7acf
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://1a399fad.agentv.pages.dev |
| Branch Preview URL: | https://chore-ci-release-workflows.agentv.pages.dev |
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
release.yml): Triggers onv*tag push. Builds, publishes all packages to npmnextchannel, then creates a GitHub Release with auto-generated release notes.promote.yml): Manual dispatch. Promotes a version fromnexttolatestdist-tag. Accepts optional version input (defaults to package.json version).Both workflows use
NPM_TOKENsecret for npm auth (generated dynamically as.npmrc— not committed).Setup required
NPM_TOKENto GitHub repo secrets (Settings > Secrets > Actions)Release flow
Test plan
NPM_TOKENsecret to the repobun run releaseto create a tag and verify the release workflow triggersnexttaglatesttag updates🤖 Generated with Claude Code