chore(swarm): move swarm-nats-auth's deps to the workspace

Per mara on the PR: all deps go into workspace level so versions stay
consistent. async-nats, data-encoding, nkeys and nats-jwt are new
[workspace.dependencies] entries; sha2 and futures-util now come from
there.

The crate had asked for sha2 0.10 while the workspace standard is 0.11,
and for the futures facade where the workspace carries futures-util. Both
resolved without adding a Cargo.lock entry - each was already in the tree
via something else - so the drift was invisible in the lock and would only
have surfaced as two versions of a hashing crate in one binary.
This commit is contained in:
atlas 2026-08-14 23:06:47 +02:00 committed by mara
commit 9b35be2a24
4 changed files with 29 additions and 28 deletions

4
Cargo.lock generated
View file

@ -4564,13 +4564,13 @@ dependencies = [
"async-nats",
"clap",
"data-encoding",
"futures",
"futures-util",
"nats-jwt",
"nkeys",
"reqwest 0.13.1",
"serde",
"serde_json",
"sha2 0.10.9",
"sha2 0.11.0",
"tokio",
"tracing",
"tracing-subscriber",