fix(deps): bump spin to 0.9.9 to clear yanked-crate warning - #2286
Merged
Conversation
spin 0.9.8 was yanked from crates.io, so `cargo audit` reported it as a yanked dependency. 0.9.9 is a semver-compatible patch release that satisfies the existing `heapless 0.7` requirement, so only the lockfile moves. The cargo-vet exemption is repinned to the new version to keep `cargo vet --locked` passing.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
bashkit | cab74c8 | Commit Preview URL Branch Preview URL |
Aug 10 2026, 09:25 AM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
spinmoves0.9.8 -> 0.9.9inCargo.lock, and the cargo-vet exemption isrepinned to match. No source changes, no API or behavior changes.
Why
spin 0.9.8was yanked from crates.io, socargo auditflagged it as a yankeddependency.
0.9.9is a semver-compatible patch release that still satisfies theexisting
heapless 0.7requirement, so only the lockfile moves — nothing else inthe graph re-resolves.
Found while sweeping the dependency tree for advisories. Everything else came back
clean:
cargo auditreports 0 vulnerabilities (even with no--ignoreflags),and
pnpm auditis clean across all five JS workspaces.Before / After
Before:
After:
The two remaining warnings are the pre-existing, already-triaged
unmaintainednotices for
atomic-polyfill(RUSTSEC-2023-0089) andproc-macro-error2(RUSTSEC-2026-0173), both ignored in
deny.toml.Supply-chain check still passes with the repinned exemption:
Also verified locally:
cargo fmt --check,cargo check --workspace --features http_client,ssh,sqlite, andcargo test --workspace --lib --features http_client,ssh,sqliteall pass.Risk
heapless 0.7->spin).spin 0.9.9is the yank-replacement for0.9.8with the same dependency set(
lock_api). Risk is limited to the embedded-Python path that pulls inheaplessviapostcard; the full CI matrix covers it.Checklist