-
-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't build 0.23.0 #1019
Comments
Thank you for notifying me on this! I will wait for upstream to publish a new patch release. Once it's published, I will update the lockfile and create another patch release for cargo-binstall. |
In the meantime, it will build with |
Potentially valuable: the yank was not due to any security issues, but because it didn't follow semver due to Drop bound. |
Looks like there may be more.
|
bumpalo and tokio-stream both released a new version after yank, so once we release a new version these warnings won't pop up. For tracing, the upstream still hasn't released a new version yet, so maybe we can revert it and then make a release. |
i'd be in favour of reverting |
I wondered whether the --locked install now pulls in dependencies that are yanked for concerning reasons. Seems that https://github.com/tokio-rs/tokio/blob/398dfda56d3ee4b0d4d9e86abe15039e86979d83/tokio-stream/CHANGELOG.md#0114-april-26th-2023 For bumpalo fitzgen/bumpalo#208 TL;DR the |
@beanow-at-crabnebula For tokio-stream, that's explained in tokio-rs/tokio#5655 TL; DR: They forgot to bump tokio dep in tokio-stream v0.1.13 |
Fixed #1019 Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>
Thanks for the patch :] |
Yes, I may try to finish a few other issues before publishing a new release, or go straight for a patch release if you'd like |
@fooooooooooooooo @qm3ster @beanow-at-crabnebula cargo-binstall v0.23.1 has released! |
tracing
0.1.38
was yanked, so the latest version doesn't buildThe text was updated successfully, but these errors were encountered: