Release: bump cua-ai 0.3.1, cua-agent 0.3.4, cua-cli 0.1.3 (playwright_execute)#37
Merged
Merged
Conversation
…ute release The playwright_execute feature spans all three packages; none are published with it yet. Bump versions (and inter-package dep pins) so the release workflows can publish cua-ai, then cua-agent, then cua-cli in dependency order. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
rgarcia
marked this pull request as ready for review
June 23, 2026 22:11
|
Firetiger deploy monitoring skipped This PR didn't match the auto-monitor filter configured on your GitHub connection:
Reason: PR is for the To monitor this PR anyway, reply with |
rgarcia
added a commit
that referenced
this pull request
Jul 8, 2026
The smoke install pulled @onkernel/cua-agent and @onkernel/cua-ai from the registry, which fails whenever a PR bumps versions ahead of publishing (this PR, and previously #37). Install all three workspace tarballs together so the packed cli resolves its workspace deps locally.
rgarcia
added a commit
that referenced
this pull request
Jul 8, 2026
* Adopt pi 0.80's instance-based Models API across cua-ai, cua-agent, cua-cli pi-ai 0.80 replaced the global api-registry and free-function catalog/stream surface (getModel, getModels, streamSimple, registerApiProvider, ...) with an instance-based Models API. Adopt it directly instead of the deprecated /compat shim: - cua-ai: new createCuaModels()/cuaModels() build a pi Models collection with pi's builtins plus CUA's adjustments: openai wrapped to dispatch the openai-cua-responses api (previous_response_id threading), google accepting GOOGLE_API_KEY or GEMINI_API_KEY, and the tzafon/yutori providers pi does not ship. registerCuaProviders() and the import-time registration side effect are gone; nothing global is mutated. - cua-ai: catalog reads go through pi's static getBuiltinModel(s); the claude-sonnet-5 and gpt-5.5 overrides are dropped now that pi-ai's registry carries both. - cua-agent: CuaAgentHarness passes a Models collection to pi-agent-core 0.80 (models option, default cuaModels()); getApiKeyAndHeaders is gone upstream. CuaAgent's default stream path is cuaModels().streamSimple. - cua-cli: buildCuaHarness takes models instead of getApiKeyAndHeaders; the scripted test fixture builds an isolated collection instead of mutating the global registry. - Bump all pi deps to 0.80.3; bump cua-ai 0.4.0, cua-agent 0.4.0, cua-cli 0.2.0 and align inter-package pins so workspaces link locally. * CI: pack workspace deps for the cli bin smoke test The smoke install pulled @onkernel/cua-agent and @onkernel/cua-ai from the registry, which fails whenever a PR bumps versions ahead of publishing (this PR, and previously #37). Install all three workspace tarballs together so the packed cli resolves its workspace deps locally. * Migrate cua-ai integration test to cuaModels().complete * Rebuild lockfile scoped to the pi dependency changes The previous lockfile was regenerated from scratch, re-resolving unrelated transitive dependencies. Rebuild it from main's lockfile with only the pi 0.80.3 bumps, workspace version changes, and the stale nested @onkernel/cua-ai registry entries removed. Verified with npm ci. * Clarify model vs models on CuaAgentHarnessOptions model selects which model runs (pi refs widened to CUA refs); models is the pi provider collection requests stream through. Mirrors pi-agent-core, which keeps both fields as separate concerns. * Name the model collection in quickstart and README snippets const models = cuaModels() with a short orientation comment reads clearer than an inline cuaModels().complete() call, and points power users at createCuaModels() for isolated collections. * Drop the gpt-5.5-2026-04-23 dated-snapshot override pi-ai's registry (generated from models.dev) only carries family roots, so the dated snapshot needed a hand-maintained override to resolve. Users pin the family id; drop the snapshot rather than maintain it. The gpt-5.5 family annotation is unchanged. --------- Co-authored-by: rgarcia <72655+rgarcia@users.noreply.github.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
1 participant
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
Version bumps to release the
playwright_executefeature (#33). That featurespans all three packages, and none are currently published with it — the live
versions (
cua-ai@0.3.0,cua-agent@0.3.3,cua-cli@0.1.2) all predate the#33 merge. So a CLI-only release won't work:
cua-clipins exact versions ofcua-ai/cua-agentwhose published builds have no playwright code.cua-aicua-agentcua-ai→ 0.3.1cua-clicua-ai→ 0.3.1,cua-agent→ 0.3.4Plus CHANGELOG entries for
cua-ai/cua-agentand a regenerated lockfile(which also picks up a pre-existing stale
cua-clilock entry, 0.1.1 → 0.1.3).Bump size: patch. The tool is a new additive feature with new public
exports, so minor bumps would be more semver-correct — easy to switch if
preferred before merge.
Release procedure (after this merges)
Push tags in dependency order, waiting for each npm publish before the
next (the agent/cli release workflows verify their deps are already on npm):
cua-ai/v0.3.1cua-agent/v0.3.4cua-cli/v0.1.3Test plan
npm run typecheck(workspace) passesnpm install; diff limited to the three version + dep refsNote
Low Risk
Release-metadata only (versions, changelogs, lockfile); no application logic changes in the diff.
Overview
This PR does not add new runtime code; it ships the
playwright_executework from #33 by bumping package versions and documenting what those releases contain.@onkernel/cua-ai0.3.0 → 0.3.1 — CHANGELOG notes the publicplaywright_executetool surface (CuaPlaywrightSchema,createCuaPlaywrightToolDefinition(), related constants/types).@onkernel/cua-agent0.3.3 → 0.3.4 — bumps itscua-aidependency to 0.3.1 and documents the opt-inplaywrightoption onCuaAgent/CuaAgentHarness(Kernel SDK Playwright/TypeScript against the live session, failures as tool content) plusPlaywrightDetails.@onkernel/cua-cli0.1.2 → 0.1.3 — pinscua-ai@0.3.1andcua-agent@0.3.4so the CLI tarball matches published agent/ai builds that include playwright.package-lock.jsonis regenerated so workspace refs align (including a stalecua-clilock entry corrected to 0.1.3).Reviewed by Cursor Bugbot for commit d3c03f8. Bugbot is set up for automated code reviews on this repo. Configure here.