Why was 1.0.10 yanked from crates.io?
dsherret opened this issue · comments
I'm just curious why 1.0.10 was yanked from crates.io? I guess old binary crates depending on a pinned old version of pin-project will no longer build?
After recent compiler changes, rustc almost always emits dead code warnings for the code generated by pin-project (#346).
It broke the minimal versions check of some projects, so, I have yanked old versions.
I guess old binary crates depending on a pinned old version of pin-project will no longer build?
No, if Cargo.lock exists it builds with a warning.
I guess old binary crates depending on a pinned old version of pin-project will no longer build?
No, if Cargo.lock exists it builds with a warning.
> cargo install deno --version 1.23.0
Downloaded deno v1.23.0
Downloaded 1 crate (3.3 MB) in 2.69s
Updating crates.io index
Installing deno v1.23.0
error: failed to compile `deno v1.23.0`, intermediate artifacts can be found at `C:\Users\david\AppData\Local\Temp\cargo-installSzOTgk`
Caused by:
failed to select a version for the requirement `pin-project = "=1.0.10"`
candidate versions found which didn't match: 1.0.11, 0.4.30, 0.3.5, ...
location searched: crates.io index
required by package `deno v1.23.0`It seems to have broken them.
Can you use --locked flag?
Yup, it works with --locked. That's not too bad then. I documented it. Thanks!
The reason it was yanked is for pedantic checks in some projects (i.e., low importance), so I reverted the yank for now.