Skip to content

chore(deps): bump agentworkforce 3.0.42 → 3.0.50 for cloud relay MCP#121

Merged
khaliqgant merged 1 commit into
mainfrom
chore/bump-agentworkforce-3.0.50-relay-mcp
Jun 6, 2026
Merged

chore(deps): bump agentworkforce 3.0.42 → 3.0.50 for cloud relay MCP#121
khaliqgant merged 1 commit into
mainfrom
chore/bump-agentworkforce-3.0.50-relay-mcp

Conversation

@khaliqgant

@khaliqgant khaliqgant commented Jun 6, 2026

Copy link
Copy Markdown
Member

User description

What

Bumps the direct agentworkforce dependencies so pear ships the cloud relay-MCP wiring:

  • agentworkforce ^3.0.42^3.0.50
  • @agentworkforce/deploy ^3.0.42^3.0.50

Regenerated package-lock.json so the full agentworkforce family resolves to 3.0.50 (@agentworkforce/runtime, persona-kit, workload-router, cli, deploy, agentworkforce).

Why

@agentworkforce/runtime@3.0.50 contains workforce#205wire Relay MCP into cloud personas — which routes both Claude and Codex cloud harnesses through agent-relay-broker mcp-args --register, merging the agent-relay MCP server into each persona's strict --mcp-config.

The lockfile previously pinned the whole agentworkforce family to 3.0.42, so npm ci installed a runtime without the relay-broker MCP wiring even though package.json floated ^3.0.42. Raising the floor + regenerating the lock is required for pear to actually pick up the fix.

Scope of the lockfile diff

  • 6 agentworkforce-family packages 3.0.423.0.50
  • A few of their nested transitive deps move within caret (@relayfile/adapter-core 0.3.320.3.35, @relayburn/sdk 8.2.08.2.1) — the normal dependency closure for 3.0.50
  • No unrelated packages touched; pear app version untouched

Not 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 (latest 8.3.0) is a separate axis; happy to do it in a follow-up if desired.

Verification

  • npm install --package-lock-only resolves the family to 3.0.50 cleanly (0 vulnerabilities, up to date)
  • Diff scoped to package.json + package-lock.json only

🤖 Generated with Claude Code


CodeAnt-AI Description

Install the agentworkforce release that includes cloud Relay MCP wiring

What Changed

  • Updates the app to use agentworkforce 3.0.50 and @agentworkforce/deploy 3.0.50
  • Refreshes the lockfile so installs pull the newer agentworkforce family, including the runtime that routes Claude and Codex cloud personas through Relay MCP
  • Brings in the related dependency updates needed for that release

Impact

✅ 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:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

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:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

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.

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

codeant-ai Bot commented Jun 6, 2026

Copy link
Copy Markdown

CodeAnt AI is reviewing your PR.

@coderabbitai

coderabbitai Bot commented Jun 6, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@khaliqgant, we couldn't start this review because you've reached your PR review rate limit.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: acf8eac4-5d4c-4660-ac09-0b168a1842bc

📥 Commits

Reviewing files that changed from the base of the PR and between 3be1190 and 321dcd7.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/bump-agentworkforce-3.0.50-relay-mcp

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

Re-trigger cubic

@codeant-ai codeant-ai Bot added the size:M This PR changes 30-99 lines, ignoring generated files label Jun 6, 2026
@khaliqgant khaliqgant merged commit b91ba12 into main Jun 6, 2026
4 checks passed
@khaliqgant khaliqgant deleted the chore/bump-agentworkforce-3.0.50-relay-mcp branch June 6, 2026 08:50
@codeant-ai

codeant-ai Bot commented Jun 6, 2026

Copy link
Copy Markdown

CodeAnt AI finished reviewing your PR.

@agent-relay-code

Copy link
Copy Markdown
Contributor

Reviewed PR #121 and fixed one real breakage: the broker’s npx fallback for AgentWorkforce personas was still pinned to agentworkforce@3.0.35 while the dependency bump moves the app to 3.0.50. Updated src/main/broker.ts to use 3.0.50, so local package resolution and fallback resolution now match.

Verified:

  • npm ci
  • npx vitest run src/main/broker.test.ts
  • npm test
  • npm run build
  • npm run verify:mcp-resources-drift
  • npx -y agentworkforce@3.0.50 --version

@agent-relay-code

Copy link
Copy Markdown
Contributor

pr-reviewer applied fixes — committed and pushed ca0d80b to this PR. The notes below describe what changed.

Reviewed PR #121 and fixed one real breakage: the broker’s npx fallback for AgentWorkforce personas was still pinned to agentworkforce@3.0.35 while the dependency bump moves the app to 3.0.50. Updated src/main/broker.ts to use 3.0.50, so local package resolution and fallback resolution now match.

Verified:

  • npm ci
  • npx vitest run src/main/broker.test.ts
  • npm test
  • npm run build
  • npm run verify:mcp-resources-drift
  • npx -y agentworkforce@3.0.50 --version

@agent-relay-code

Copy link
Copy Markdown
Contributor

Fixed the PR issue I found: the broker fallback npx path still pinned agentworkforce@3.0.35 while this PR bumps the bundled dependency to 3.0.50. That would use the old CLI whenever Pear can’t find a local/PATH install.

Changed:

Verified locally:

  • npm ci
  • npx vitest run src/main/broker.test.ts
  • throwaway fallback command: npx -y agentworkforce@3.0.50 --version -> 3.0.50
  • npm run verify:mcp-resources-drift
  • npm test
  • npm run build

@agent-relay-code

Copy link
Copy Markdown
Contributor

⚠️ pr-reviewer push failed (exit 1) — fixes were not applied to the PR. The notes below are advisory and were not pushed.

Fixed the PR issue I found: the broker fallback npx path still pinned agentworkforce@3.0.35 while this PR bumps the bundled dependency to 3.0.50. That would use the old CLI whenever Pear can’t find a local/PATH install.

Changed:

Verified locally:

  • npm ci
  • npx vitest run src/main/broker.test.ts
  • throwaway fallback command: npx -y agentworkforce@3.0.50 --version -> 3.0.50
  • npm run verify:mcp-resources-drift
  • npm test
  • npm run build

@agent-relay-code

Copy link
Copy Markdown
Contributor

Reviewed PR #121 and fixed the issue I found: the dependency bump updated agentworkforce to 3.0.50, but the broker’s npx fallback still generated agentworkforce@3.0.35. I updated the fallback pin, added a regression test that keeps it aligned with package.json, and tightened a couple of dynamic broker-event type guards in the same touched file.

Validation run:

  • npm ci
  • npx vitest run src/main/broker.test.ts
  • npm test
  • focused production typecheck for src/main/broker.ts and src/main/proactive-agent.bundle.ts
  • npm run build
  • npm run verify:mcp-resources-drift
  • npx -y agentworkforce@3.0.50 --version

npx tsc -b still fails on broad pre-existing repo typecheck issues unrelated to this PR, but the repo build and touched-area checks pass.

@agent-relay-code

Copy link
Copy Markdown
Contributor

⚠️ pr-reviewer push failed (exit 1) — fixes were not applied to the PR. The notes below are advisory and were not pushed.

Reviewed PR #121 and fixed the issue I found: the dependency bump updated agentworkforce to 3.0.50, but the broker’s npx fallback still generated agentworkforce@3.0.35. I updated the fallback pin, added a regression test that keeps it aligned with package.json, and tightened a couple of dynamic broker-event type guards in the same touched file.

Validation run:

  • npm ci
  • npx vitest run src/main/broker.test.ts
  • npm test
  • focused production typecheck for src/main/broker.ts and src/main/proactive-agent.bundle.ts
  • npm run build
  • npm run verify:mcp-resources-drift
  • npx -y agentworkforce@3.0.50 --version

npx tsc -b still fails on broad pre-existing repo typecheck issues unrelated to this PR, but the repo build and touched-area checks pass.

@agent-relay-code

Copy link
Copy Markdown
Contributor

Fixed one validated issue in src/main/broker.ts: the AgentWorkforce npx fallback version now matches the PR’s bumped agentworkforce dependency, 3.0.50, instead of the stale 3.0.35.

Verified:

  • npm ci
  • npx vitest run src/main/broker.test.ts
  • npm test
  • npm run build
  • npm run verify:mcp-resources-drift
  • fallback command smoke test: npx -y agentworkforce@3.0.50 --version returned 3.0.50

Notes:

  • npx tsc -p tsconfig.node.json --noEmit and npx tsc -p tsconfig.web.json --noEmit surface existing unrelated project type errors outside this PR’s dependency bump.
  • npm run verify:mcp-spawn expects a packaged dist directory and failed because that artifact is not present after the normal build.

@agent-relay-code

Copy link
Copy Markdown
Contributor

pr-reviewer applied fixes — committed and pushed ca0d80b to this PR. The notes below describe what changed.

Fixed one validated issue in src/main/broker.ts: the AgentWorkforce npx fallback version now matches the PR’s bumped agentworkforce dependency, 3.0.50, instead of the stale 3.0.35.

Verified:

  • npm ci
  • npx vitest run src/main/broker.test.ts
  • npm test
  • npm run build
  • npm run verify:mcp-resources-drift
  • fallback command smoke test: npx -y agentworkforce@3.0.50 --version returned 3.0.50

Notes:

  • npx tsc -p tsconfig.node.json --noEmit and npx tsc -p tsconfig.web.json --noEmit surface existing unrelated project type errors outside this PR’s dependency bump.
  • npm run verify:mcp-spawn expects a packaged dist directory and failed because that artifact is not present after the normal build.

@agent-relay-code

Copy link
Copy Markdown
Contributor

Reviewed PR #121 and made one required fix outside the original changed-file set:

Updated src/main/broker.ts so Pear’s npx fallback launches agentworkforce@3.0.50, matching the bumped agentworkforce dependency. Without this, users lacking a local/PATH CLI would still run 3.0.35.

Local verification passed:

  • npm ci
  • npx vitest run src/main/broker.test.ts
  • npm test
  • npx tsc --noEmit
  • npm run verify:mcp-resources-drift
  • npm run build

@agent-relay-code

Copy link
Copy Markdown
Contributor

pr-reviewer applied fixes — committed and pushed ca0d80b to this PR. The notes below describe what changed.

Reviewed PR #121 and made one required fix outside the original changed-file set:

Updated src/main/broker.ts so Pear’s npx fallback launches agentworkforce@3.0.50, matching the bumped agentworkforce dependency. Without this, users lacking a local/PATH CLI would still run 3.0.35.

Local verification passed:

  • npm ci
  • npx vitest run src/main/broker.test.ts
  • npm test
  • npx tsc --noEmit
  • npm run verify:mcp-resources-drift
  • npm run build

kjgbot pushed a commit that referenced this pull request Jun 6, 2026
* 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M This PR changes 30-99 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant