✅ Deploy Preview for shepmaster-snafu ready!

Name	Link
🔨 Latest commit	5b5f80d
🔍 Latest deploy log	https://app.netlify.com/sites/shepmaster-snafu/deploys/6650ba38dd594f0008f6551e
😎 Deploy Preview	https://deploy-preview-451--shepmaster-snafu.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Away from computer at the moment, but I think I want this to be default-features=false, have the version range be >= 0.4, < 0.6, and then probably add a test that it continues to work with version 0.4. 0.5 will be tested in CI automatically.

and then probably add a test

We already have that, yay.

Hi there -- as you might be aware, there's a long-standing issue with Cargo (rust-lang/cargo#5529) where specifying a too-wide version of a dependency can cause cargo updates to flap around between the old and the new versions. Would you be okay just saying heck 0.5 and dropping support for 0.4?

as you might be aware

I was not, so thanks for the heads up!

a long-standing issue with Cargo

I actually thought about fixing the bug in Cargo instead of working around it in my crate. However, the reproduction case in that issue doesn’t work anymore. Since you presumably saw this recently, do you have a way to reliably reproduce the problem?

Sure -- we noticed it in one of our (Oxide's) larger repos:

git clone https://github.com/oxidecomputer/omicron
cd omicron
git checkout 38cb5542
cargo update -p clap --precise 4.5.21

On x86_64 Linux, this series of commands produces this diff: https://gist.github.com/sunshowers/2973e27d91f17d1a92f6a1fe026ee79c. I'm guessing it's the same on other platforms as well though I haven't verified it.

As you can see, the snafu-derive -> heck dependency got updated from 0.5 to 0.4. (I've also observed it go the other way.)