fai/chain-module-sdk-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(workspace): drop the strict =0.1.0 pin on fai-module-sdk-macros
All checks were successful
CI / Linux x86_64 (Forgejo) (push) Successful in 1m33s
Details

Browse source 
The previous commit (eb7a1d5) bumped the workspace version to
0.1.1 but kept the SDK's dep on the macros crate pinned at
exactly 0.1.0. Result: cargo refused to resolve a workspace
build because the path-resolved macros crate was 0.1.1 while
the dep required =0.1.0. The Cargo.lock from that commit
landed unchanged from the pre-bump state, masking the
breakage in CI artifacts but failing on a fresh build.

Drop the strict pin and use path-only resolution for now,
matching the convention used by tokio/tokio-macros and similar
workspace pairings. The two crates will still move in lockstep
because they share a workspace.package version line.

Bumps the workspace patch version 0.1.1 -> 0.1.2 per the
per-commit policy.

Signed-off-by: flemming-it <sf@flemming.it>
This commit is contained in:
flemming-it 2026-05-01 14:58:35 +02:00
parent eb7a1d5d42
commit f209fbc86f
3 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

2
crates/fai-module-sdk/Cargo.toml
View file

@ -10,7 +10,7 @@ rust-version.workspace = true
description = "Stable, ergonomic surface for writing F∆I Platform modules in Rust"
[dependencies]
fai-module-sdk-macros = { path = "../fai-module-sdk-macros", version = "=0.1.0" }
fai-module-sdk-macros = { path = "../fai-module-sdk-macros" }
serde = { workspace = true }
serde_json = { workspace = true }
thiserror = { workspace = true }