fix(ci): add release-please version markers to hyperdb-mcp#41
Merged
StefanSteiner merged 1 commit intoMay 26, 2026
Merged
Conversation
The `hyperdb-api` dependency in `hyperdb-mcp/Cargo.toml` was pinned to `0.1.1` without release-please markers. When release-please bumped the workspace to 0.2.0, cargo couldn't resolve the stale pin. Add the `x-release-please-start-version` / `end` markers and register the file in `release-please-config.json` extra-files so it gets bumped automatically on future releases.
Merged
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.
Summary
x-release-please-start-version/x-release-please-endmarkers around thehyperdb-apidependency inhyperdb-mcp/Cargo.tomland pins it to=0.1.3(matching the workspace version)hyperdb-mcp/Cargo.tomlinrelease-please-config.jsonextra-filesso it gets version-bumped automatically on future releasesProblem
The release-please PR bumps the workspace to
0.2.0, buthyperdb-mcpstill depended onhyperdb-api = "^0.1.1". Cargo couldn't resolve this because the path dep was now0.2.0. All CI jobs (clippy, publish dry-run, platform builds) failed with:Test plan
cargo check -p hyperdb-mcppasses locally with workspace version at 0.1.3