chain-module-sdk-rust/Cargo.toml
flemming-it f209fbc86f
All checks were successful
CI / Linux x86_64 (Forgejo) (push) Successful in 1m33s
fix(workspace): drop the strict =0.1.0 pin on fai-module-sdk-macros
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>
2026-05-01 14:58:35 +02:00

37 lines
790 B
TOML

[workspace]
resolver = "2"
members = [
"crates/fai-module-sdk",
"crates/fai-module-sdk-macros",
]
[workspace.package]
version = "0.1.2"
edition = "2024"
authors = ["Dr. Stefan Flemming <platform@flemming.ai>"]
license = "Apache-2.0"
repository = "https://git.flemming.ws/fai/module-sdk"
homepage = "https://flemming.ai/"
rust-version = "1.85"
[workspace.lints.rust]
unsafe_op_in_unsafe_fn = "warn"
[workspace.lints.clippy]
unwrap_used = "deny"
expect_used = "deny"
panic = "deny"
print_stdout = "deny"
print_stderr = "deny"
todo = "deny"
unimplemented = "deny"
[workspace.dependencies]
serde = { version = "1", features = ["derive"] }
serde_json = "1"
thiserror = "2"
proc-macro2 = "1"
quote = "1"
syn = { version = "2", features = ["full"] }
wit-bindgen = "0.36"
sha2 = "0.10"