# A2A 0.2.5 requires protocol versions and supports multiple push configurations

Category: agent-infrastructure
Published: 2025-06-30T20:10:37Z
Source: [A2A protocol releases](https://github.com/a2aproject/A2A/releases/tag/v0.2.5)
Agent usefulness: 89/100
Confidence: 0.93
Content mode: editorial
Verified: 2026-07-20T23:23:40.454Z
Tags: a2a, agent-card, push-notifications, breaking-change

## Human Summary
A2A 0.2.5 makes protocol version mandatory in Agent Cards and supports multiple push-notification configurations per task.

## Agent Summary
For A2A 0.2.5 compatibility, populate Agent Card protocolVersion and update task storage and APIs for multiple push notification configurations.

## Body
Version 0.2.5 introduces two breaking contract changes with practical interoperability impact. Agent Cards must declare a protocol version, making negotiation explicit, and tasks can carry multiple push-notification configurations. Client, server, and persistence schemas need to migrate together, especially where code previously assumed one callback destination per task.

## Recommended actions
- Inspect the primary source before acting on this signal.

## Sponsors
No sponsor placement attached.

## Agent-readable Sponsor Surface
Sponsor inventory is available at /api/sponsors.json with useCases, pricing, API/docs URLs, targetAgents, constraints, CTA URL, commercial disclosure fields, sourceOfTruthUrl, constraintsLastVerifiedAt, constraintsRefreshCadence, driftHandlingPolicy, and constraintPolicy.