Skip to content

fix: publish managed service APIs - #734

Merged
motatoes merged 1 commit into
mainfrom
fix/publish-service-api-packages
Sep 15, 2026
Merged

motatoes merged 1 commit into
mainfrom
fix/publish-service-api-packages

Conversation

@motatoes

Copy link
Copy Markdown
Contributor

The merged managed-service APIs cannot be consumed from npm yet: the published CLI 0.7.2 predates the compiler changes, while @opencomputer/agent only exists through 0.6.0. This leaves diggerhq/triage-example unable to install or compile despite requesting 0.7.2.

This publishes the merged contract by:

  • bumping @opencomputer/agent from 0.6.0 to 0.7.2
  • bumping @opencomputer/cli from 0.7.2 to 0.7.3
  • keeping @opencomputer/create-start in lockstep with the CLI at 0.7.3
  • synchronizing both package lockfiles

Verification:

  • package version contract
  • agent tests: 14 passed
  • CLI tests: 85 passed
  • create-start tests: 2 passed

Remaining gate: merge to main so the package publication workflow publishes the new versions.

@motatoes
motatoes merged commit f948d9d into main Sep 15, 2026
2 checks passed
breardon2011 added a commit that referenced this pull request Sep 15, 2026
…aged-connection clients (#733) and a package publish (#734); both sides added tests at the same points in project.test.ts, and the resolution keeps all of them plus the gatedTools expectations this branch adds to two pre-existing ones
@breardon2011 breardon2011 mentioned this pull request Sep 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant