Closed str4d closed 4 months ago
Thanks for reporting and the detailed analysis.
The possible solutions are also appreciated - even though fixing the breakage may cause more breakage with those who use 2.8 with HTTP1, that should be the minority and doing so should be preferred.
A fix as proposed is in the works.
This crate documents itself as following SemVer: https://github.com/frewsxcv/rust-crates-index/blob/dba8b144d222b7da41ed57df613d93575905b2b5/CHANGELOG.md?plain=1#L1-L6
Per SemVer, migrating from
crates-index 2.8.0
tocrates-index 2.10.0
should only involve backwards-compatible changes. However,2.10.0
included #170 which migrated fromhttp 0.2
tohttp 1.0
. This is a breaking change, becausehttp
is exposed in the crate's public API. For example,crates_index::SparseIndex::parse_cache_response
takes anhttp::response::Response
as an argument.Specifically, this update broke users' ability to install
cargo-dl
(which usesSparseIndex::parse_cache_response
), which now fails with:Possible resolutions:
2.Y.Z
series. Then re-publish 2.10.0 / currentmaster
branch as 3.0.0.crates-index
follows SemVer from the changelog, and update the changelog for2.10.0
to document that it is a breaking release that migrates fromhttp 0.2
tohttp 1
.