Skip to content

fix(sdk): export A2A communicate subpaths#753

Merged
khaliqgant merged 1 commit intomainfrom
miya/relay-a2a-exports
Apr 19, 2026
Merged

fix(sdk): export A2A communicate subpaths#753
khaliqgant merged 1 commit intomainfrom
miya/relay-a2a-exports

Conversation

@miyaontherelay
Copy link
Copy Markdown
Contributor

@miyaontherelay miyaontherelay commented Apr 19, 2026

Summary

  • export the existing A2A communicate modules from @agent-relay/sdk
  • expose a2a-types, a2a-server, a2a-transport, and a2a-bridge as supported SDK subpaths
  • unblock downstream consumers like Sage from using A2A support without local imports or copied code

Why

The A2A implementation already exists in Relay source, but the SDK package export surface does not expose it. Downstream consumers hit runtime/module resolution failures like:

  • Missing "./communicate/a2a-transport" specifier in "@agent-relay/sdk" package

This fixes the actual upstream package boundary instead of papering over it downstream.

Validation

  • attempted clean-worktree SDK build validation
  • clean worktree surfaced a broader existing workspace/local-package resolution issue around @agent-relay/config, unrelated to this export change
  • the export fix itself is focused and isolated to packages/sdk/package.json

Open in Devin Review

Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

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

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

Open in Devin Review

@khaliqgant khaliqgant merged commit 4579ec3 into main Apr 19, 2026
40 checks passed
@khaliqgant khaliqgant deleted the miya/relay-a2a-exports branch April 19, 2026 15:00
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.

2 participants