ST-2026-231 · Runtimes & developer platforms
Atlassian moves Forge Rovo Agent Connector to Preview and requires A2A v1.0
Atlassian moved the Forge Rovo Agent Connector from EAP to Preview, enabled production and staging deployment, and made A2A v1.0 mandatory; deployments that remain on A2A v0.3 are rejected.
Previous state
The Forge Rovo Agent Connector was available through the Early Access Program, and A2A v0.3-era connector implementations had not yet reached the newly enforced Preview deployment boundary.
Current state
The Rovo Agent Connector is in Preview and can be deployed to production and staging. Atlassian requires A2A v1.0; apps still using v0.3 are rejected at deployment, and Atlassian directs developers to Forge CLI v13.3 or later for the transition.
Affected users
Who needs to care
Forge developers with Rovo Agent Connector apps, particularly existing EAP implementations still using A2A v0.3.
Required response
What to do
Set protocols.agent2Agent.version to 1.0, migrate the JSON-RPC implementation to A2A v1.0, and use Forge CLI v13.3 or later before deploying an affected connector app.
Evidence boundary
What the source does not prove
Atlassian proves the Rovo Agent Connector Preview transition and the A2A v1.0 deployment requirement for this module. It does not impose A2A v1.0 on unrelated Forge modules or every Atlassian integration.
Lifecycle history
Dated event sequence
- Rovo Agent Connector moved to Preview
Atlassian moved the module from EAP to Preview, enabled production/staging deployment, and made A2A v1.0 mandatory for deployment.
Evidence ledger
First-party sources
- 01Atlassian — Forge changelog — Rovo Agent Connector EAP to Preview
Official Atlassian Forge changelog · 2026-08-25
Open official source ↗