From d3dc5c54dc4bf64f9f2a224be22224965f5821bf Mon Sep 17 00:00:00 2001 From: Stefan Steiner Date: Mon, 1 Jun 2026 19:47:34 -0700 Subject: [PATCH] fix(release): wrap hyperdb-compile-check pin in release-please markers The optional `hyperdb-compile-check = "=0.3.1"` dependency in hyperdb-api-derive/Cargo.toml was the only internal exact-version pin in the workspace NOT wrapped in `# x-release-please-start-version` / `# x-release-please-end` markers. release-please therefore bumped hyperdb-compile-check's own version (and every other internal pin) to the new release version but left this consumer pin at =0.3.1, making the workspace unresolvable: error: failed to select a version for the requirement `hyperdb-compile-check = "=0.3.1"` candidate versions found which didn't match: 0.4.0 required by package `hyperdb-api-derive` This broke the v0.4.0 release-please PR (#95): clippy, all three test matrices, cargo-deny, publish-dry-run, and node-bindings all failed on dependency resolution. Wrapping the pin lets release-please bump it in lockstep with the rest of the workspace, as it already does for the hyperdb-api dev-dependency pin a few lines below. --- hyperdb-api-derive/Cargo.toml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/hyperdb-api-derive/Cargo.toml b/hyperdb-api-derive/Cargo.toml index a5938b3..24f7225 100644 --- a/hyperdb-api-derive/Cargo.toml +++ b/hyperdb-api-derive/Cargo.toml @@ -26,7 +26,9 @@ compile-time = ["dep:hyperdb-compile-check"] syn = { version = "2", features = ["full"] } quote = "1" proc-macro2 = "1" +# x-release-please-start-version hyperdb-compile-check = { path = "../hyperdb-compile-check", version = "=0.3.1", optional = true } +# x-release-please-end [dev-dependencies] # x-release-please-start-version