v0.4.2

Fixes the release pipeline so published releases actually carry downloadable binaries and a Docker image. No changes to the CLI or MCP server behaviour.

Customer-facing changes

• Release assets are now published: ado-mcp and ado-cli for Linux x86_64, macOS x86_64/arm64, and Windows x86_64, plus a multi-arch Docker image at ghcr.io/like-a-freedom/rusty-azure-devops (v0.4.0/v0.4.1 shipped no assets).

Fixed issues

• Release builds failed with cannot stat target/.../release/rusty_azure_devops — the package ships two binaries (ado-mcp, ado-cli), and the workflow now publishes both for every platform.
• The Docker image build failed at cargo fetch; the build stage now creates placeholder targets before fetching dependencies.

Full Changelog: v0.4.1...v0.4.2

v0.4.1

No changes to the CLI or MCP server behaviour — this release wires up the automated release pipeline.

Customer-facing changes

• GitHub Releases now ship prebuilt binaries for Linux x86_64, macOS x86_64/arm64, and Windows x86_64, plus a multi-arch Docker image at ghcr.io/like-a-freedom/rusty-azure-devops (previous releases published no assets).

Other

• CI runs only on release and manual dispatch — no workflows on push or pull requests.
• GitHub Actions updated to latest (checkout v7, cache v6, setup-rust-toolchain v2, codecov v7, docker v4/v7, action-gh-release v3).
• Dependabot version-update pull requests disabled.

Full Changelog: v0.4.0...v0.4.1

v0.4.0

No breaking changes — both ado-mcp and ado-cli are drop-in replacements for v0.3.0.

Customer-facing changes

• New ado-cli login / ado-cli logout: first-run authentication prompts for the base URL and PAT, validates them against the server, and writes ~/.config/rusty_azure_devops/config.yaml with mode 0600 — no more hand-editing a config file with a plaintext secret.
• Login is agent- and headless-friendly: --token-stdin keeps the PAT out of argv and shell history; prompts fire only on a TTY so unattended runs never hang; --json returns success and failure in one shape (errors on stderr as {"ok":false,"reason","detail","hint"} with empty stdout); exit codes are 0 ok / 2 usage / 3 needs --force / 1 other; success prints a next verify command.

Fixed issues

• ado-cli login with a malformed --base-url crashed with exit 101; it now returns a validation_failed error envelope and exit 1.

Other

• Dependencies updated to latest: rmcp 3.5.1, jsonschema 0.58.6, tokio 1.53.3, reqwest 0.13.5, schemars 1.2.3, thiserror 2.0.21, serde_json 1.0.154, rand 0.10.3.
• Toolchain policy is now stable (rust-toolchain.toml); the fixed component list was removed.

Full Changelog: v0.3.0...v0.4.0