chore(deps): use youtrack-client from youtrack-cli v0.4.0 #2

Merged

David merged 1 commit from chore/youtrack-client-v0.4.0 into main

2026-05-31 20:21:37 +02:00

David commented

2026-05-31 20:19:51 +02:00

Owner

What

Switch the youtrack-client dependency from a local path to a git dependency pinned to the youtrack-cli v0.4.0 tag, the first release that contains the crates/ workspace.

youtrack-client = { git = "https://dev.a8n.run/pandoras-box/youtrack-cli.git", tag = "v0.4.0" }

Why

The path dependency (../youtrack-cli/crates/youtrack-client) worked only for local builds. CI (check.yml) and the Docker build-binary* workflows have this repo alone as their build context, so they could not resolve the sibling path. The git+tag dep resolves everywhere and mirrors how forgejo-mcp pins fj-client. The crate's workspace = true deps resolve from the youtrack-cli workspace root the git clone brings.

Verification

cargo build, cargo fmt --check, cargo clippy --all-targets all clean against the git source.
Cargo.lock now records a git+https://dev.a8n.run/pandoras-box/youtrack-cli source; no path dep remains.
MCP stdio server still initializes and lists all tools.
v0.4.0 tag confirmed to contain crates/youtrack-client/Cargo.toml.

Also retires the "outstanding dependency" blocker note in CLAUDE.md.

## What Switch the `youtrack-client` dependency from a local path to a git dependency pinned to the youtrack-cli `v0.4.0` tag, the first release that contains the `crates/` workspace. ```toml youtrack-client = { git = "https://dev.a8n.run/pandoras-box/youtrack-cli.git", tag = "v0.4.0" } ``` ## Why The path dependency (`../youtrack-cli/crates/youtrack-client`) worked only for local builds. CI (`check.yml`) and the Docker `build-binary*` workflows have this repo alone as their build context, so they could not resolve the sibling path. The git+tag dep resolves everywhere and mirrors how forgejo-mcp pins `fj-client`. The crate's `workspace = true` deps resolve from the youtrack-cli workspace root the git clone brings. ## Verification - `cargo build`, `cargo fmt --check`, `cargo clippy --all-targets` all clean against the git source. - `Cargo.lock` now records a `git+https://dev.a8n.run/pandoras-box/youtrack-cli` source; no path dep remains. - MCP stdio server still initializes and lists all tools. - v0.4.0 tag confirmed to contain `crates/youtrack-client/Cargo.toml`. Also retires the "outstanding dependency" blocker note in `CLAUDE.md`.

David added 1 commit

2026-05-31 20:19:51 +02:00

chore(deps): use youtrack-client from youtrack-cli v0.4.0

Check / fmt + clippy + build + tests (pull_request) Successful in 19s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

9d7308c3fb

Replace the path dependency on ../youtrack-cli/crates/youtrack-client with a git dependency pinned to the youtrack-cli v0.4.0 tag, the first release that contains the crates/ workspace. The path dep worked only for local builds; the git+tag dep resolves in CI (check.yml) and the Docker build-binary* workflows, whose build context is this repo alone. Its workspace = true deps resolve from the youtrack-cli workspace root that the git clone brings, matching how forgejo-mcp pins fj-client.

Verified: cargo build, cargo fmt --check, and cargo clippy --all-targets all clean against the git source; the MCP stdio server still initializes and lists 30 tools. Updated CLAUDE.md to retire the outstanding-dependency blocker.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>