fix: bundle @agent-relay/cloud (not published at lockstep version)#790
Closed
willwashburn wants to merge 1 commit intomainfrom
Closed
fix: bundle @agent-relay/cloud (not published at lockstep version)#790willwashburn wants to merge 1 commit intomainfrom
willwashburn wants to merge 1 commit intomainfrom
Conversation
@agent-relay/cloud is the only workspace package whose npm namespace isn't owned by this repo's publish flow. The publish-packages job in publish.yml has every other internal package (sdk, hooks, config, telemetry, trajectory, user-directory, utils) but cloud is absent. Latest registry version is 2.0.23, not 6.x. Under the previous bundled-everything model this was invisible: the workspace cloud at version 6.0.1 got bundled into the agent-relay tarball and users never tried to fetch from registry. After unbundling, agent-relay's regular dep on @agent-relay/cloud@6.0.1 caused install to fail with ETARGET because that version doesn't exist on npm. Fix: keep cloud bundled. It's safe — cloud's only @agent-relay dependency is @agent-relay/config (also at 6.0.1, also published normally). It's not in the SDK chain, so bundling cloud doesn't re-introduce the broker shadow-copy problem we just spent five commits eliminating. Verified end-to-end: a fresh install of the locally-packed tarball produces a tree where cloud/config sit bundled inside agent-relay/node_modules/@agent-relay/, while sdk and the broker optional-dep package hoist correctly to the top-level node_modules/@agent-relay/, and the broker binary at node_modules/@agent-relay/broker-darwin-arm64/bin/agent-relay-broker is a real Mach-O executable. Tarball size: 1.5 MB → 4.0 MB (cloud's @aws-sdk/client-s3 transitive deps are most of the increase). Still 6× smaller than the original 24.2 MB. Long-term, the cleanest fix is to publish @agent-relay/cloud from this repo at the lockstep version (or rename the workspace to avoid the namespace collision). For now, bundling restores correctness. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
Member
Author
4 tasks
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
agent-relay@6.0.1was published, butnpm install agent-relay@6.0.1fails on every platform with:@agent-relay/cloudis the only workspace package whose npm namespace isn't owned by this repo's publish flow. Thepublish-packagesjob in.github/workflows/publish.ymlships every other internal package (sdk, hooks, config, telemetry, trajectory, user-directory, utils) but cloud is absent from the matrix. The latest registry version of@agent-relay/cloudis2.0.23, not 6.x.Under the previous bundled-everything model this was invisible: the workspace cloud at the lockstep version got bundled into the agent-relay tarball and users never tried to fetch from registry. After #788 unbundled
@agent-relay/*, agent-relay's regular dep on@agent-relay/cloud@6.0.1causesnpm installto fail because that version doesn't exist on npm.Fix
Keep
@agent-relay/cloudbundled. It's safe — cloud's only@agent-relaydependency is@agent-relay/config(also at 6.0.1, also published normally), and cloud is not in the SDK chain, so bundling it doesn't re-introduce the broker shadow-copy problem #788 just spent five commits eliminating.Verification
Locally packed this branch and installed into a scratch project. Tree:
Tarball size: 1.5 MB → 4.0 MB. Most of the increase is cloud's
@aws-sdk/client-s3transitive deps. Still 6× smaller than the original 24.2 MB pre-#788.Long-term follow-ups
@agent-relay/cloudfrom this repo at the lockstep version (figure out the namespace ownership story), or rename the workspace to avoid the collision. For now bundling restores correctness without picking a side.Test plan
npm install agent-relay@<new>succeeds on a fresh machine and the broker spawns.🤖 Generated with Claude Code