chore(release): Bump version to 0.6.0

[arcaputo3]

Summary

Release v0.6.0 version bump.

Changes since v0.5.0

• feat(dsl): provider-independent DSL with type-safe capabilities (feat(dsl): provider-independent DSL with type-safe capabilities #33) — Agent[-P,-I,+O], ExecutionPolicy, AgentBuilder with phantom capability types, ClaudeInterpreter/CodexInterpreter/A2AInterpreter, TraceSummary, Evaluation with composable Utility scoring
• feat(dsl): safe defaults, structured output, directory scope, auto permissions (feat(dsl): directory scope enforcement, auto permissions, cross-provider structured output #34) — No tools by default, ToolSurface presets, StructuredOutput.derive macro, DirectoryScope with PreToolUse hook enforcement, Peano-encoded delegation depth with compile-time DepthLTE checks
• chore: bump mill-bun-plugin to 0.2.0 (chore: bump mill-bun-plugin to 0.2.0 with bun macro + CLAUDE.md rewrite #35) — Compile-time validated bun"" dependency specifiers, BunPublishModule embeds META-INF/bun/bun-dependencies.json for automatic transitive npm dependency resolution

Version updates

• build.mill: 0.5.1-SNAPSHOT → 0.6.0
• README.md: 0.5.0 → 0.6.0 (Mill, sbt, Maven coordinates)

Test plan

• ./mill agent.compile passes
• ./mill agent.test — 49 suites, 0 failures
• No SNAPSHOT references in build files

Post-merge

After merge, create annotated tag v0.6.0 on the merge commit and push to trigger release workflow. Then bump to 0.6.1-SNAPSHOT.

🤖 Generated with Claude Code

[claude]

PR Review: chore(release): Bump version to 0.6.0

Overall this is a clean, minimal release bump. The changes are consistent across all four README.md coordinates and build.mill. A few observations:

Correctness ✅

All version references are updated correctly:

• README.md header badge: 0.5.0 → 0.6.0
• Mill, SBT, and Maven dependency examples: all updated
• build.mill publishVersion default: 0.5.1-SNAPSHOT → 0.6.0

No stale 0.5.x references remain in tracked files.

Minor Concern: Fallback version is now a release version

override def publishVersion = Task.Input {
  Task.env.get("PUBLISH_VERSION").getOrElse("0.6.0")
}

Convention is for the local fallback to be a SNAPSHOT (e.g. 0.6.1-SNAPSHOT) so that local ./mill agent.publishLocal builds are clearly distinguishable from official Maven Central releases. With the current change, a developer who runs publishLocal without setting PUBLISH_VERSION will overwrite a 0.6.0 artifact in their local cache that is indistinguishable from the officially published one.

The "Post-merge" note in the PR description covers this (bump to 0.6.1-SNAPSHOT), but that bump should ideally land in a quick follow-up PR right after merge — before anyone does a local publish. Consider opening that PR now as a draft to make the dependency explicit.

Post-merge checklist

The manual tag step is easy to miss under pressure. Worth considering whether the release workflow could be triggered by a version bump commit pattern (e.g. a release/* branch) rather than requiring a manual git tag -a ... after merge. Not a blocker for this PR, just a future automation opportunity.

Nit: RELEASING.md examples

docs/RELEASING.md still uses 0.1.0 as the example version throughout. Keeping docs in sync with current conventions would help new contributors. Pre-existing issue, out of scope here.

---

Verdict: Approve with the suggestion to queue a 0.6.1-SNAPSHOT follow-up bump before any local publishing happens.