Release 0.6.10

[thenorili]

Updates changelog and version references for release 0.6.10

[qwandor]

It looks like this was just yanked with no compatible version available, which causes some builds to fail. What's going on? Will there be a 0.6.11 shortly?

[yaahc]

the last version accidentally introduced a breakage: https://github.com/eyre-rs/eyre/pull/95

Tho I'm honestly surprised that yanking that version causes builds to fail. I would have expected it to fall back to 0.6.9, can you link to an example of a broken build so I can understand how yanking it still causes issues? We hadn't realized there was an urgency to get the rerelease back out.

[dtolnay]

Everything that declares a dependency on eyre 0.6.10 will fail. There are 68 results on GitHub: https://github.com/search?q=%2Feyre+%3D+%220.6.10%22%2F&type=code. It will not fall back to 0.6.9.

Unfortunately this is widespread as projects use bots to bump the dependency numbers immediately after releases are made available, even if the projects would otherwise build perfectly fine against the older version. I have not seen any of those bots monitor and correct for yanked crates.

• https://github.com/alsuren/mijia-homie/pull/435
• https://github.com/arxanas/git-branchless/pull/1149
• https://github.com/aschey/vercel-tokei/pull/53
• https://github.com/auguwu/sentry-eyre/pull/16
• https://github.com/bluez-rs/bluez-async/pull/204
• https://github.com/charted-dev/charted/pull/1326
• https://github.com/charted-dev/emails/pull/215
• https://github.com/csunibo/course-description-merged/pull/24
• https://github.com/evenfurther/aoc/pull/55
• https://github.com/gifnksm/git-http-server/pull/239
• https://github.com/johnallen3d/conditions/pull/154
• https://github.com/matter-labs/zksync-withdrawal-finalizer/pull/332
• https://github.com/MolotovCherry/virtual-display-rs/pull/51
• https://github.com/Noelware/hazel/pull/385
• https://github.com/Noelware/noeldoc/pull/108
• https://github.com/qwandor/dancelist/pull/299
• https://github.com/qwandor/octopower/pull/191
• https://github.com/rgreinho/labelr-rs/pull/87
• https://github.com/talzion12/http-cache/pull/154
• https://github.com/Zilliqa/zq2/pull/610

[dtolnay]

Example failure: https://github.com/evenfurther/aoc/actions/runs/7189388139/job/19580870459

error: failed to select a version for the requirement `eyre = "^0.6.10"`
candidate versions found which didn't match: 0.6.9, 0.6.8, 0.6.7, ...
location searched: crates.io index
required by package `aoc v0.1.0 (/home/runner/work/aoc/aoc/aoc)`
if you are looking for the prerelease package it needs to be specified explicitly
    eyre = { version = "0.6.1-rc.1" }
perhaps a crate was updated and forgotten to be re-vendored?

[yaahc]

Unfortunately this is widespread as projects use bots to bump the dependency numbers immediately after releases are made available, even if the projects would otherwise build perfectly fine against the older version. I have not seen any of those bots monitor and correct for yanked crates.

unfortunate indeed, and good to know, thank you. I'll go ahead and expedite getting that re-release out asap.

[yaahc]

should be good now: https://crates.io/crates/eyre/versions