fix(build): sync Cargo.lock youtrack-mcp version to 0.2.1 #26

Merged

David merged 1 commit from fix/sync-cargo-lock-0.2.1 into main

2026-06-23 05:10:07 +02:00

David commented

2026-06-23 05:09:33 +02:00

Owner

Problem

main is inconsistent: Cargo.toml is 0.2.1 but Cargo.lock's youtrack-mcp entry is still 0.2.0, so every cargo build --release --locked against main (and the v0.2.1 tag) fails. This is why the v0.2.1 binary build broke.

Root cause: the Release v0.2.1 commit (88f1b05) was cut from pre-fix main (02c9e04), before the create-release lockfile fix (#24) merged. The old recipe bumped only the manifest and never synced the lock. The fixed recipe later reached the release branch via a merge, but the release commit itself predated it, so the lock was never updated for this cut.

Fix

Hand-sync Cargo.lock's youtrack-mcp version to 0.2.1 (third-party pins untouched), the same one-time cleanup #22 applied for 0.2.0. Verified cargo check --locked and the full just pre-commit gate (fmt, clippy, build, 73 tests) pass.

Going forward

The recipe fix (#24) is now on main, so the next release cut with just create-release runs cargo update --package youtrack-mcp --precise <version> and stages Cargo.lock in the release commit automatically. No more manual syncs. After this merges, cut a fresh just create-release hotfix (v0.2.2) for a clean, buildable release.

#YTMCP-18

## Problem `main` is inconsistent: `Cargo.toml` is `0.2.1` but `Cargo.lock`'s `youtrack-mcp` entry is still `0.2.0`, so every `cargo build --release --locked` against `main` (and the v0.2.1 tag) fails. This is why the v0.2.1 binary build broke. Root cause: the `Release v0.2.1` commit (88f1b05) was cut from pre-fix `main` (02c9e04), before the create-release lockfile fix (#24) merged. The old recipe bumped only the manifest and never synced the lock. The fixed recipe later reached the release branch via a merge, but the release commit itself predated it, so the lock was never updated for this cut. ## Fix Hand-sync `Cargo.lock`'s `youtrack-mcp` version to `0.2.1` (third-party pins untouched), the same one-time cleanup #22 applied for 0.2.0. Verified `cargo check --locked` and the full `just pre-commit` gate (fmt, clippy, build, 73 tests) pass. ## Going forward The recipe fix (#24) is now on `main`, so the next release cut with `just create-release` runs `cargo update --package youtrack-mcp --precise <version>` and stages `Cargo.lock` in the release commit automatically. No more manual syncs. After this merges, cut a fresh `just create-release hotfix` (v0.2.2) for a clean, buildable release. #YTMCP-18

David added 1 commit

2026-06-23 05:09:33 +02:00

fix(build): sync Cargo.lock youtrack-mcp version to 0.2.1

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

Details

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

Details

79432de6db

The v0.2.1 release commit (88f1b05) was cut from pre-fix main (02c9e04), before the create-release lockfile fix (#24) merged, so it bumped Cargo.toml to 0.2.1 but left Cargo.lock pinned at 0.2.0. Main is now inconsistent and every `cargo build --release --locked` against it fails, which is why the v0.2.1 binary build broke.

Sync Cargo.lock's youtrack-mcp entry to 0.2.1 to match the manifest (third-party pins untouched), the same hand-sync #22 applied for 0.2.0. The next release cut with the fixed recipe will keep the lock in step automatically, so this manual sync is one-time cleanup for the 0.2.1 cut.

Signed-off-by: David Randall <David@NiceGuyIT.biz>

#YTMCP-18