You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The crates.io crate is severely outdated and no longer supported. It doesn't support signatures properly, which caused a bunch of issues in Rust recently when trying to add a new josh subtree, where the crates.io version was used accidentally. This would have been prevented if it was yanked.
Do you think it would make sense to yank the crates.io versions?
The text was updated successfully, but these errors were encountered:
Hi, thanks for that report. You are right of course, having those unmaintained for so long is not good.
I have yanked them for now.
I think if we put them back up on crates.io they should be split up into josh-filter, josh-core and josh-proxy as separate creates alongside with automated upload (like we do with hub.docker).
The crates.io crate is severely outdated and no longer supported. It doesn't support signatures properly, which caused a bunch of issues in Rust recently when trying to add a new josh subtree, where the crates.io version was used accidentally. This would have been prevented if it was yanked.
Do you think it would make sense to yank the crates.io versions?
The text was updated successfully, but these errors were encountered: