GUID: CHANGE-3405
Published: Tue, 25 Aug 2026 05:51:09 GMT
Category: Added
What's changing
The rovo:agentConnector module has moved from EAP to Preview. Apps using it can now deploy to production and staging environments, enabling Marketplace listing. Key changes:
- A2A v1.0 is now required — v0.3 is no longer supported. Apps still on v0.3 are rejected at deployment. Manifest must declare
version: "1.0" under protocols.agent2Agent.
- System user mentionability change — adding
rovo:agentConnector makes the app's system user non-mentionable; the agent connector user takes its place. Forge CLI v13.3+ warns and prompts for approval at deploy time.
- Requires Forge CLI v13.3+.
Impact on forge-sim parity
- Manifest/modules: if/when forge-sim recognizes
rovo:agentConnector, manifest validation should require protocols.agent2Agent.version: "1.0" and reject v0.3 (matching real deploy rejection). Now that the module is Preview (deployable to prod), it's in scope for simulation, not EAP-fenced.
- Deploy semantics: the CLI approval prompt for the system-user mentionability change is a deploy-time behavior; low priority for the simulator but relevant if forge-sim's deploy path validates rovo modules.
- Simulator area: modules / manifest validation (and potentially the deploy pipeline).
Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3405
GUID: CHANGE-3405
Published: Tue, 25 Aug 2026 05:51:09 GMT
Category: Added
What's changing
The
rovo:agentConnectormodule has moved from EAP to Preview. Apps using it can now deploy to production and staging environments, enabling Marketplace listing. Key changes:version: "1.0"underprotocols.agent2Agent.rovo:agentConnectormakes the app's system user non-mentionable; the agent connector user takes its place. Forge CLI v13.3+ warns and prompts for approval at deploy time.Impact on forge-sim parity
rovo:agentConnector, manifest validation should requireprotocols.agent2Agent.version: "1.0"and reject v0.3 (matching real deploy rejection). Now that the module is Preview (deployable to prod), it's in scope for simulation, not EAP-fenced.Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3405