chore(deps): bump agentworkforce 3.0.42 → 3.0.50 for cloud relay MCP#121
Conversation
Pulls @agentworkforce/runtime@3.0.50, which wires the Relay MCP server into cloud personas for both Claude and Codex harnesses (workforce #205). The lockfile previously pinned the whole agentworkforce family to 3.0.42, so `npm ci` installed a runtime without the relay-broker MCP wiring. Bump the two direct deps (agentworkforce, @agentworkforce/deploy) and regenerate the lock so the family resolves to 3.0.50. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
CodeAnt AI is reviewing your PR. |
|
Warning Review limit reached
More reviews will be available in 26 minutes and 8 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Code Review
This pull request updates the project dependencies in package.json and package-lock.json. Specifically, it upgrades @agentworkforce/deploy and agentworkforce from version 3.0.42 to 3.0.50, which cascades into updating other internal @AgentWorkforce packages and transitive dependencies like @relayfile/adapter-core, get-east-asian-width, and string-width. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
CodeAnt AI finished reviewing your PR. |
|
Reviewed PR #121 and fixed one real breakage: the broker’s Verified:
|
|
✅ pr-reviewer applied fixes — committed and pushed Reviewed PR #121 and fixed one real breakage: the broker’s Verified:
|
|
Fixed the PR issue I found: the broker fallback Changed:
Verified locally:
|
|
Fixed the PR issue I found: the broker fallback Changed:
Verified locally:
|
|
Reviewed PR #121 and fixed the issue I found: the dependency bump updated Validation run:
|
|
Reviewed PR #121 and fixed the issue I found: the dependency bump updated Validation run:
|
|
Fixed one validated issue in src/main/broker.ts: the AgentWorkforce Verified:
Notes:
|
|
✅ pr-reviewer applied fixes — committed and pushed Fixed one validated issue in src/main/broker.ts: the AgentWorkforce Verified:
Notes:
|
|
Reviewed PR #121 and made one required fix outside the original changed-file set: Updated src/main/broker.ts so Pear’s Local verification passed:
|
|
✅ pr-reviewer applied fixes — committed and pushed Reviewed PR #121 and made one required fix outside the original changed-file set: Updated src/main/broker.ts so Pear’s Local verification passed:
|
* chore(deps): bump agentworkforce 3.0.42 -> 3.0.50 for cloud relay MCP Pulls @agentworkforce/runtime@3.0.50, which wires the Relay MCP server into cloud personas for both Claude and Codex harnesses (workforce #205). The lockfile previously pinned the whole agentworkforce family to 3.0.42, so `npm ci` installed a runtime without the relay-broker MCP wiring. Bump the two direct deps (agentworkforce, @agentworkforce/deploy) and regenerate the lock so the family resolves to 3.0.50. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * chore: apply pr-reviewer fixes for #121 * Fix relayfile mount binary install publish * chore: apply pr-reviewer fixes for #128 * chore: apply pr-reviewer fixes for #128 --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Co-authored-by: agent-relay-code[bot] <agent-relay-code[bot]@users.noreply.github.com>
User description
What
Bumps the direct
agentworkforcedependencies so pear ships the cloud relay-MCP wiring:agentworkforce^3.0.42→^3.0.50@agentworkforce/deploy^3.0.42→^3.0.50Regenerated
package-lock.jsonso the full agentworkforce family resolves to 3.0.50 (@agentworkforce/runtime,persona-kit,workload-router,cli,deploy,agentworkforce).Why
@agentworkforce/runtime@3.0.50contains workforce#205 — wire Relay MCP into cloud personas — which routes both Claude and Codex cloud harnesses throughagent-relay-broker mcp-args --register, merging theagent-relayMCP server into each persona's strict--mcp-config.The lockfile previously pinned the whole agentworkforce family to
3.0.42, sonpm ciinstalled a runtime without the relay-broker MCP wiring even thoughpackage.jsonfloated^3.0.42. Raising the floor + regenerating the lock is required for pear to actually pick up the fix.Scope of the lockfile diff
3.0.42→3.0.50@relayfile/adapter-core0.3.32→0.3.35,@relayburn/sdk8.2.0→8.2.1) — the normal dependency closure for 3.0.50Not included
@agent-relay/*(^8.1.2) is left as-is — the broker that services the cloud persona MCP path is provided by the Daytona sandbox image, not pear's local deps. Bumping the relay SDKs (latest8.3.0) is a separate axis; happy to do it in a follow-up if desired.Verification
npm install --package-lock-onlyresolves the family to 3.0.50 cleanly (0 vulnerabilities,up to date)package.json+package-lock.jsononly🤖 Generated with Claude Code
CodeAnt-AI Description
Install the agentworkforce release that includes cloud Relay MCP wiring
What Changed
agentworkforce3.0.50 and@agentworkforce/deploy3.0.50Impact
✅ Cloud personas use Relay MCP during installs✅ Fewer missing MCP connections in Claude and Codex harnesses✅ More reliable cloud relay setup💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.