Re: v0.5 Migration Issues

[EditUndo]

Hi All,

I wanted to acknowledge the concerns that have been raised regarding the difficulty migrating through these last few releases.

I appreciate that it's been a challenge and we are putting in place measures to ensure the stability of future releases with clear migration paths.

That being said, we've gained a lot of insights from recent Agent deployments and it was determined that significant changes to the SDKs architecture would be necessary to support all of the new capabilities introduced in the latest updates to the A2A protocol in addition to the new features we've added to the projects roadmap.

As a result, I deemed it critical to remove as much technical debt as possible during the re-arch.

Meaning de-coupling A2A agents from the transport layer, sunsetting support for Jayson, introducing a service - based pattern for discovery and streamlining the design around agent execution.

While these changes were challenging, they have resulted in an SDK that's more modular, flexible and stable.

Thanks for your support,
pbj

P.S. We're always keen for constructive feedback so please let us know if you have any recommendations on improving the overall quality of the code base.