Add npm release workflows for CUA packages - #11
Merged
Conversation
rgarcia
marked this pull request as ready for review
May 13, 2026 20:50
|
Firetiger deploy monitoring skipped This PR didn't match the auto-monitor filter configured on your GitHub connection:
Reason: PR modifies npm release workflows for CUA packages, not kernel API endpoints or Temporal workflows as specified in the filter. To monitor this PR anyway, reply with |
rgarcia
force-pushed
the
hypeship/npm-release-workflows
branch
3 times, most recently
from
May 13, 2026 21:06
ef93bc4 to
30e39e0
Compare
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
Testing
Release note
The package names are not currently published on npm. npm requires a package to exist before configuring trusted publishing, so the initial package bootstrap still needs to be handled before tag-based trusted publishing can run.
Note
Medium Risk
Adds automated npm publishing via GitHub Actions tags, which can unintentionally publish bad versions if tagging/version checks are wrong. Mitigated by enforcing tag-on-
main, matching tag/package versions, running build/tests, and packing before publish.Overview
Introduces tag-triggered GitHub Actions workflows to publish
@onkernel/cua-aiand@onkernel/cua-agentto npm fromcua-ai/v*andcua-agent/v*tags, including checks that the tag points to a commit onmain, matchespackage.jsonversion, and that builds/tests/npm pack --dry-runpass.For
@onkernel/cua-agent, the workflow additionally verifies the pinned@onkernel/cua-aidependency version is already published before releasing.Updates package publish metadata (adds
license,repository/bugs/homepage, andpublishConfig.access=public) and adds operational docs (docs/npm-releases.mdand.agents/skills/release/SKILL.md) describing trusted publishing setup, versioning, tagging, and release steps.Reviewed by Cursor Bugbot for commit 30e39e0. Bugbot is set up for automated code reviews on this repo. Configure here.