flemming-it
f209fbc86f
All checks were successful
CI / Linux x86_64 (Forgejo) (push) Successful in 1m33s
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>
23 lines
586 B
TOML
23 lines
586 B
TOML
[package]
|
|
name = "fai-module-sdk"
|
|
version.workspace = true
|
|
edition.workspace = true
|
|
authors.workspace = true
|
|
license.workspace = true
|
|
repository.workspace = true
|
|
homepage.workspace = true
|
|
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" }
|
|
serde = { workspace = true }
|
|
serde_json = { workspace = true }
|
|
thiserror = { workspace = true }
|
|
wit-bindgen = { workspace = true }
|
|
|
|
[dev-dependencies]
|
|
sha2 = { workspace = true }
|
|
|
|
[lints]
|
|
workspace = true
|