chore(release): Bump version to 0.10.1

[arcaputo3]

Prep PR for the 0.10.1 patch release.

Contains the version bump only; the actual fix (#58 / #59) is already on main. After this merges, an annotated v0.10.1 tag on the squash-merged commit triggers the Maven Central release workflow.

Changes

• build.mill — publish-version fallback 0.11.0-SNAPSHOT → 0.10.1
• README.md — install/version refs 0.10.0 → 0.10.1, plus a ### 0.10.1 Notes section

What 0.10.1 ships

Exactly one change beyond 0.10.0: the A2A request-body-cap fix (#59) — the JVM server now applies the configured maxRequestBodyBytes (was silently capped at zio-http's 100 KiB default → 413 on inline file uploads), and the default is raised 1 MiB → 64 MiB.

Verification

• ./mill show agent.publishVersion → 0.10.1
• ./mill agent.test → 326/326 pass (both platforms)

🤖 Generated with Claude Code

[claude]

Review: chore(release) Bump version to 0.10.1

Clean, well-scoped release-prep PR. I verified the changes against the repo state and everything is consistent. Nothing blocking. 🟢

Version consistency — All 0.10.0 / 0.11.0-SNAPSHOT references are now 0.10.1. Confirmed there are no stragglers:

• build.mill:71 fallback to 0.10.1 ✅
• README.md SDK baseline line, Mill, SBT, and Maven snippets all bumped ✅
• grep across .md/.mill/.scala/.json shows no remaining 0.10.0/0.11.0 references outside the intentional "0.10.0 Notes" history section ✅

The shipped fix is actually on the base — commit c9a516b "fix(a2a): wire maxRequestBodyBytes into zio-http; raise default to 64 MiB (#59)" is present on the merge base, so the PR body claim ("the actual fix is already on main") holds. The release notes accurately describe the change:

• A2AServerLive.scala:147 wires config.maxRequestBodyBytes via disableRequestStreaming(...), replacing the silent zio-http 100 KiB RequestStreaming.Disabled default ✅
• A2AServerDefaults.MaxRequestBodyBytes = 64 * 1024 * 1024 (shared, so JS/Bun inherits it as the notes claim) ✅
• Test coverage exists for the wiring (A2AServerLiveSpec.scala:674, A2ARestTransportSpec.scala:493/527) ✅

Minor observations (non-blocking)

1. The 0.11.0-SNAPSHOT to 0.10.1 fallback is correct for cutting the release, but worth remembering to bump the fallback back to a SNAPSHOT (e.g. 0.10.2-SNAPSHOT / 0.11.0-SNAPSHOT) on main after the tag is pushed, so post-release local/CI builds are not accidentally stamped as the released 0.10.1. Since the release is driven by the PUBLISH_VERSION env var in CI, the fallback only affects local publishLocal, but it is an easy footgun to leave behind.

2. Release notes accuracy is excellent — the base64 ~33% inflation rationale and the fileWithUri guidance for larger payloads are genuinely useful for consumers. Nice touch.

3. No CHANGELOG.md in the repo — the README "Notes" sections serve that role. Just noting the convention so future releases keep appending here consistently.

Verdict

Low-risk, mechanical version bump backed by an already-landed, tested fix. The PR body verification claims (publishVersion to 0.10.1, 326/326 tests) are consistent with what I can see. LGTM. 🚀