pandoras-box/youtrack-mcp
Archived
Watch
8
0
Fork
You've already forked youtrack-mcp
 0
Code Issues Pull requests Projects Releases 3 Packages 1 Wiki Activity Actions

fix(build): sync Cargo.lock youtrack-mcp version to 0.2.0 #22

Merged
David merged 2 commits from fix/YTMCP-18-stale-cargo-lock-version into main 2026-06-23 01:32:43 +02:00
Conversation 0 Commits 2 Files changed 2 +11 -6
David commented 2026-06-23 01:12:35 +02:00
Owner
Copy link

Problem

build-binary-static.yml on main (run #109, commit 0270e23f) failed at the cargo build --release --locked cache-priming step with: error: cannot update the lock file because --locked was passed to prevent this.

Root cause

The v0.2.0 release (650eec1) bumped version in Cargo.toml from 0.1.0 to 0.2.0 but Cargo.lock still recorded the youtrack-mcp package at 0.1.0. Cargo treats the root package version as part of the lock, so the mismatch forces a re-lock, which --locked forbids. This is not a youtrack-cli git-dependency drift: tag = v0.4.0 resolves to 4edbe18 in both Cargo.toml and Cargo.lock, matching the remote tag.

Fix

Update the single recorded version line in Cargo.lock (0.1.0 to 0.2.0). No other dependency changes. Verified with cargo build --locked --offline (succeeds, touching only that line) and the full just pre-commit gate (fmt, clippy, build, 73 tests, all green).

#YTMCP-18

## Problem `build-binary-static.yml` on `main` (run #109, commit `0270e23f`) failed at the `cargo build --release --locked` cache-priming step with: `error: cannot update the lock file because --locked was passed to prevent this`. ## Root cause The v0.2.0 release (`650eec1`) bumped `version` in `Cargo.toml` from `0.1.0` to `0.2.0` but `Cargo.lock` still recorded the `youtrack-mcp` package at `0.1.0`. Cargo treats the root package version as part of the lock, so the mismatch forces a re-lock, which `--locked` forbids. This is not a `youtrack-cli` git-dependency drift: `tag = v0.4.0` resolves to `4edbe18` in both `Cargo.toml` and `Cargo.lock`, matching the remote tag. ## Fix Update the single recorded version line in `Cargo.lock` (`0.1.0` to `0.2.0`). No other dependency changes. Verified with `cargo build --locked --offline` (succeeds, touching only that line) and the full `just pre-commit` gate (fmt, clippy, build, 73 tests, all green). #YTMCP-18
fix(build): sync Cargo.lock youtrack-mcp version to 0.2.0
All checks were successful
Check / fmt + clippy + build + tests (pull_request) Successful in 21s
Details
8d15078149 
The v0.2.0 release bumped the package version in Cargo.toml but left Cargo.lock recording youtrack-mcp at 0.1.0. cargo build --locked treats the root package version as part of the lock, so the mismatch forced a re-lock that --locked forbids, failing build-binary-static.yml on main with "cannot update the lock file because --locked was passed". Updating the single recorded version line restores a consistent lock; cargo build --locked --offline now succeeds touching only that line.

#YTMCP-18
chore: Sync the checks and justfile recipes
All checks were successful
Check / fmt + clippy + build + tests (pull_request) Successful in 21s
Details
Create release / Create release from merged PR (pull_request) Has been skipped
Details
cc404c7446 
Signed-off-by: David Randall <David@NiceGuyIT.biz>
David merged commit 02c9e044a3 into main 2026-06-23 01:32:43 +02:00
David deleted branch fix/YTMCP-18-stale-cargo-lock-version 2026-06-23 01:32:43 +02:00
Commenting is not possible because the repository is archived.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pandoras-box/youtrack-mcp!22
No description provided.