fix(build): sync Cargo.lock with 0.2.0 version bump #24

Merged

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

2026-06-22 19:14:36 +02:00

David commented

2026-06-22 19:13:25 +02:00

Owner

Problem

The build-binary.yml release build failed on the v0.2.0 tag at cargo build --release --locked with cannot update the lock file Cargo.lock because --locked was passed. The v0.2.0 release commit bumped Cargo.toml to version = "0.2.0" but left the committed Cargo.lock pinning forgejo-mcp at 0.1.0, so the lock is out of sync with the manifest and --locked refuses to proceed.

Fix

Regenerate the forgejo-mcp entry in Cargo.lock to 0.2.0 (one line) so the lock matches Cargo.toml. Verified with cargo metadata --locked (passes) and the full just pre-commit suite (fmt, clippy, build, test all green).

Follow-up (release re-trigger)

This restores the lock on main but does not re-run the failed release. Per the FJMCP-18 triage, after merge the v0.2.0 tag must be deleted and re-created (or bumped) so the tag points at the fixed commit and the release build re-triggers. That tag/release step is the maintainer's to take.

Fixes FJMCP-18.

## Problem The `build-binary.yml` release build failed on the `v0.2.0` tag at `cargo build --release --locked` with `cannot update the lock file Cargo.lock because --locked was passed`. The `v0.2.0` release commit bumped `Cargo.toml` to `version = "0.2.0"` but left the committed `Cargo.lock` pinning `forgejo-mcp` at `0.1.0`, so the lock is out of sync with the manifest and `--locked` refuses to proceed. ## Fix Regenerate the `forgejo-mcp` entry in `Cargo.lock` to `0.2.0` (one line) so the lock matches `Cargo.toml`. Verified with `cargo metadata --locked` (passes) and the full `just pre-commit` suite (fmt, clippy, build, test all green). ## Follow-up (release re-trigger) This restores the lock on `main` but does not re-run the failed release. Per the FJMCP-18 triage, after merge the `v0.2.0` tag must be deleted and re-created (or bumped) so the tag points at the fixed commit and the release build re-triggers. That tag/release step is the maintainer's to take. Fixes FJMCP-18.

David added 1 commit

2026-06-22 19:13:25 +02:00

fix(build): sync Cargo.lock with 0.2.0 version bump

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

Details

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

Details

0cd16c12db

The v0.2.0 release bumped the package version in Cargo.toml to 0.2.0 but left the committed Cargo.lock pinning forgejo-mcp at 0.1.0. The Docker build runs cargo build --release --locked, which refuses to update the lock and fails with 'cannot update the lock file Cargo.lock because --locked was passed'. Regenerate the forgejo-mcp entry to 0.2.0 so the lock matches Cargo.toml and --locked succeeds.

#FJMCP-18