A maintainer’s checklist for releasing versions of the A2A Java project. It covers version changes, automated checks, tags, Maven Central publication, follow-up development versions, and documentation.

Use it to prepare a release, verify CI, publish a version, create the next snapshot version, and plan documentation changes.

It reduces missed release steps and helps keep published packages, source control, and documentation aligned.

How a2aproject/a2a-java configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to a2aproject/a2a-java. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/a2aproject/a2a-java/main/.agents/skills/release-a2a/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/a2aproject/a2a-java

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/a2aproject/a2a-java/release-a2a/github.svg)](https://agentmods.dev/skills/a2aproject/a2a-java/release-a2a)

Your own site

<a href="https://agentmods.dev/skills/a2aproject/a2a-java/release-a2a"><img src="https://agentmods.dev/badge/skills/a2aproject/a2a-java/release-a2a/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/a2aproject/a2a-java/release-a2a"><img src="https://agentmods.dev/badge/skills/a2aproject/a2a-java/release-a2a.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,502 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00036	$0.02502
Opus 5.5	$0.00014	$0.01001
Sonnet 5.5	$0.00007	$0.00500
Haiku 4.5	$0.00004	$0.00250

Measured 10d ago against content hash bb0bea1ccecc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-a2a scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/release-a2a/SKILL.md · 232 lines

How it starts

The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Process

Guide the full release lifecycle. Proceed autonomously through mechanical steps (running scripts, polling CI, creating PRs) and pause only for genuine decisions, failures, or destructive actions.

Phase 0: Determine Release Parameters

Read the current version from the root pom.xml — the -SNAPSHOT suffix indicates the current dev version.
Ask the user which version to release if not already specified.
Apply the Final suffix convention: if the user specifies a plain version like 1.2.0, the release version is 1.2.0.Final. Pre-release qualifiers (Alpha1, Beta1, CR1) are used as-is.
Suggest a sensible next SNAPSHOT version and confirm with the user:
- Final: 1.1.0.Final → 1.1.1.Final-SNAPSHOT
- Pre-release: 1.1.0.Alpha1 → 1.1.0.Alpha2-SNAPSHOT
Determine the documentation plan:
- Skip for micro/patch releases (X.Y.Z where Z > 0)
- Ask for pre-releases (Alpha/Beta/CR)
- Yes for major/minor Final releases (X.Y.0.Final)
Detect git remotes. Run git remote -v and identify:
- Upstream remote: the remote whose URL contains a2aproject/a2a-java (this is the canonical repo — it may be called upstream, origin, or anything else).
- Fork remote: a different remote owned by the current user (typically origin). Extract the fork owner from its URL (e.g., kabir from github.com:kabir/a2a-java.git).
Throughout this skill, <upstream> refers to the detected upstream remote name and <fork> refers to the fork remote name. All PRs are created from the fork, and tags/main are pushed to/pulled from upstream.

Phase 1: Pre-Release Verification

Verify gh CLI is installed and authenticated:
```
gh auth status
```
If not installed or not logged in, stop and ask the user to run gh auth login.
Verify clean working tree:
```
git status
```
If there are uncommitted changes, stop and ask.
Verify we are on main and in sync with upstream. Fetch first to ensure the remote ref is current:
```
git fetch <upstream> main
git log --oneline HEAD..<upstream>/main
git log --oneline <upstream>/main..HEAD
```
If local main is behind or ahead of <upstream>/main, stop and ask the user.

Read the full file on GitHub · 232 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago Changed · +2 lines bb0bea1ccecc
2mo ago First seen · 230 lines · 36 tokens per session scan A e5de10c9d339

Subscribe to this mod's changes

release-a2a is a skill published in the GitHub repository a2aproject/a2a-java (509 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 2,502 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

CI and CD DevOps and cloud Git and workflow Releases a2a a2a-client a2a-server agent2agent ai hacktoberfest

release-a2a next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
release-a2aa2aproject/a2a-java	Skill	509	yesterday	Apache-2.0	A	36	Claude Code
prime-silo-devopsbinary16labs/prime-silo	Skill	5	13d ago	MIT	A	46	Claude Code, Codex
github-release-managementruvnet/RuView	Skill	103k	yesterday	MIT	A	27	Claude Code
agent-github-modesruvnet/ruflo	Skill	81k	yesterday	MIT	A	21	Claude Code
xberg-releasexberg-io/xberg	Skill	9.5k	yesterday	MIT	A	16	Claude Code, Codex
factory-shipBuilderIO/skills	Skill	4.6k	4d ago	MIT	A	28	Claude Code
releaseprcompozy/compozy	Skill	2.8k	yesterday	MIT	A	53	Claude Code, Codex

a2a-java: Skill for Claude Code