Skip to content

Update yanked futures-util and spin in Cargo.lock - #68

Merged
heitor-lassarote merged 1 commit into
masterfrom
heitor-lassarote/#67-update-yanked-deps
Oct 15, 2026
Merged

heitor-lassarote merged 1 commit into
masterfrom
heitor-lassarote/#67-update-yanked-deps

Conversation

@heitor-lassarote

Copy link
Copy Markdown
Member

Description

cargo update moves futures-util 0.3.30 to 0.3.31 and spin 0.9.8 to 0.9.9, because both old versions are yanked on crates.io. futures-sink and futures-task move to 0.3.34 with futures-util. Only Cargo.lock changes. None of the new versions is yanked, and cargo test passes.

Related issue(s)

Fixed #67

🤖 Generated with Claude Code

Problem: `Cargo.lock` pins `futures-util` 0.3.30 and `spin` 0.9.8.
Both versions are yanked on crates.io. Cargo warns about yanked
versions in a lockfile, and the first publish should not ship them.

Solution: `cargo update` them to the nearest unyanked releases,
`futures-util` 0.3.31 and `spin` 0.9.9. `futures-util` pulls
`futures-sink` and `futures-task` to 0.3.34 with it. None of the new
versions is yanked, and `cargo test` passes.
@heitor-lassarote
heitor-lassarote marked this pull request as ready for review October 14, 2026 13:57
@heitor-lassarote
heitor-lassarote merged commit ff87251 into master Oct 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update yanked futures-util and spin in Cargo.lock

2 participants