Uploaded November 2026 | Updated November 2026, 3 hours ago
My Rust Programming Cargo pattern for work-in-progress crates.
I used to mark unreleased versions as "0.7.4-WIP". The problem: that's a semver pre-release, so a dependent crate asking for genai "0.7.3" won't match it, and [patch.crates-io] gets silently ignored.
This isn't specific to -WIP. Any pre-release suffix, like -alpha, -beta, -rc.1 or -dev, has the same effect: Cargo won't match it against a normal version requirement unless the dependent explicitly asks for that pre-release. So a git patch with a pre-release version is skipped.
The fix:
- Keep the real next version: e.g., version = "0.7.4"
- Add publish = false # WIP so it can't be published by accident
- Remove or comment out that line when you cut the release
Now the git patch matches, and the whole dependency tree uses one copy of the crate.
Then I show how I use this in my production Rust lib (genai) and CLI (aipack).
By the way, my consulting company now focuses on helping teams ship production Rust.
➜ britesnow.com
(15 years of production expertise, brought to your team)
Links related to this video:
➜ genai: github.com/jeremychone/rust-genai
➜ aipack: aipack.ai
➜ britesnow.com
=== More Links
➜ Helping teams ship production Rust - britesnow.com
(15 years of production coding expertise, brought to your team)
➜ pro@coder tutorial (current JC coding harness)
news.aipack.ai/p/procoder-v052-demo-workbench
➜ JC Twitter - twitter.com/jeremychone
➜ Discord JC general-rust - discord.gg/W2besKCzjx
➜ Discord JC Live Streaming - discord.gg/nEnG4ryBku
➜ Discord JC genai & aipack & procoder - discord.gg/6KkpQBKGFS
My Rust Programming Cargo pattern for work-in-progress crates.
I used to mark unreleased versions as "0.7.4-WIP". The problem: that's a semver pre-release, so a dependent crate asking for genai "0.7.3" won't match it, and [patch.crates-io] gets silently ignored.
This isn't specific to -WIP. Any pre-release suffix, like -alpha, -beta, -rc.1 or -dev, has the same effect: Cargo won't match it against a normal version requirement unless the dependent explicitly asks for that pre-release. So a git patch with a pre-release version is skipped.
The fix:
- Keep the real next version: e.g., version = "0.7.4"
- Add publish = false # WIP so it can't be published by accident
- Remove or comment out that line when you cut the release
Now the git patch matches, and the whole dependency tree uses one copy of the crate.
Then I show how I use this in my production Rust lib (genai) and CLI (aipack).
By the way, my consulting company now focuses on helping teams ship production Rust.
➜ britesnow.com
(15 years of production expertise, brought to your team)
Links related to this video:
➜ genai: github.com/jeremychone/rust-genai
➜ aipack: aipack.ai
➜ britesnow.com
=== More Links
➜ Helping teams ship production Rust - britesnow.com
(15 years of production coding expertise, brought to your team)
➜ pro@coder tutorial (current JC coding harness)
news.aipack.ai/p/procoder-v052-demo-workbench
➜ JC Twitter - twitter.com/jeremychone
➜ Discord JC general-rust - discord.gg/W2besKCzjx
➜ Discord JC Live Streaming - discord.gg/nEnG4ryBku
➜ Discord JC genai & aipack & procoder - discord.gg/6KkpQBKGFS







