Repository navigation
v0.3.3
Fixes the binary reporting the wrong version — releases v0.3.1 and v0.3.2 both shipped as 0.3.0.
What was broken
The binary from the v0.3.1 release printed openproxy 0.3.0. Not cosmetic: the same constant is served in the A2A agent card and the MCP serverInfo handshake, so a connecting agent was told the wrong version for two releases.
Cause
Cargo.toml is bumped by hand, but clap's bare version in the derive reads CARGO_PKG_VERSION. Tag v0.3.2 was cut from a tree whose Cargo.toml still said 0.3.0, so every version-reporting surface inherited the stale value.
Fix
build.rsresolves the version in precedence order: CI tag (GITHUB_REF_NAME) → nearest git tag →CARGO_PKG_VERSION, exported asOPENPROXY_VERSION.- Tagged local builds with no tag still fall back to
Cargo.toml— correct, since there is no release to name. - A
cargo:warningfires when the tag andCargo.tomldisagree, so the next drift is visible at build time instead of arriving as a user bug report. - Wired through every surface that reports a version:
--version, the startup banner,a2a.rs(agent card + health skill + task info), andmcp/server.rs(serverInfo, health tool,openproxy://healthresource).
Upgrade recommended for anyone running agents that check the reported version.
Full Changelog: v0.3.2...v0.3.3