Unify CLI release and prerelease publishing#62
Merged
Conversation
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-cua-cli.ymltrusted-publishing workflowcua-aiandcua-agentinto prerelease tarballs so cross-workspace changes are exercisedWhy
npm permits one trusted GitHub Actions workflow per package. Keeping both publish paths in
release-cua-cli.ymllets them share the existing OIDC publisher identity while the manual path rejectslatestand publishes only under an explicit prerelease dist-tag.Testing
actionlint .github/workflows/release-cua-cli.ymlcua-ai,cua-agent, andcua-cliThe npm publish step was not run locally.
Note
Medium Risk
Touches npm publish and OIDC release automation; prerelease path skips production-only gates (ptywright build, unit tests) and publishes bundled workspace versions under custom dist-tags.
Overview
Merges CLI prerelease publishing into
release-cua-cli.ymland deletesprerelease-cua-cli.ymlso npm trusted publishing uses a single workflow per package.Production path (
pushoncua-cli/v*tags) is unchanged in spirit: tag-on-main, package version vs tag check, Zig/ptywright native build, dependency checks against npm, CLI unit tests, workspace pack, and defaultnpm publish.Manual prerelease path (
workflow_dispatchwith a non-latestdist_tag) bumps the CLI to<base>-<dist-tag>.<run-number>, skips native ptywright build and full CLI tests, packs branch-built@onkernel/cua-aiand@onkernel/cua-agentinto the CLI tarball viabundledDependencies, smoke-tests install including bundled paths, and publishes with--tag <dist_tag>. Concurrency groups now includegithub.event_nameso tag and manual runs do not collide incorrectly.Reviewed by Cursor Bugbot for commit 1fc5754. Bugbot is set up for automated code reviews on this repo. Configure here.