fix(release): bump inter-crate version pins during release#55
Merged
Conversation
The version bump steps stamped each crate's own [package] version from the
git tag but left inter-crate path-dependency pins untouched. cli, mcp, and
wasm pin vastlint-core = { path, version = "X" } (needed for crates.io
publish), so bumping core to a new minor broke the ^X requirement and failed
every build-cli target with "failed to select a version for vastlint-core".
Extend both bump steps to also rewrite the path-dependency version pins.
Path-only deps (ffi, nif) are left untouched.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
aleksUIX
added a commit
that referenced
this pull request
Jun 20, 2026
The version bump steps stamped each crate's own [package] version from the
git tag but left inter-crate path-dependency pins untouched. cli, mcp, and
wasm pin vastlint-core = { path, version = "X" } (needed for crates.io
publish), so bumping core to a new minor broke the ^X requirement and failed
every build-cli target with "failed to select a version for vastlint-core".
Extend both bump steps to also rewrite the path-dependency version pins.
Path-only deps (ffi, nif) are left untouched.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The v0.6.0 release run failed on all 8
build-clitargets:The
Bump crate versions to match git tagsteps rewrote each crate's own[package]version =from the tag, but not the inter-crate path-dependency pins.vastlint-cli,-mcp, and-wasmdeclarevastlint-core = { path = "...", version = "0.5.0" }(the version is required socargo publishcan resolve it on crates.io). Bumping core to0.6.0left those pins at^0.5.0, which excludes0.6.0, so cargo refused to build.build-ffiandbuild-nifpassed because they pinvastlint-coreby path only (no version).Fix
Both bump steps now also rewrite the path-dependency version pins to the release version. Path-only deps are untouched. Verified locally against all six crate manifests: package versions and the cli/mcp/wasm core pins go to the new version, ffi/nif stay path-only.
After merge: delete and re-push the
v0.6.0tag (no artifacts were published in the failed run, all publish jobs were skipped).🤖 Generated with Claude Code