while the deprecation notice is clearly visible in the README on github it is not visible on crates.io and will thus probably be missed by many (by all appearances on crates.io it's still the correct tool to use).
it'd be great if you could release a final v0.30.1 to crates.io just to get the README published there.
optionally you could maybe even print a deprecation notice to STDOUT (or STDERR?) on each application invocation so that those which just update it via cargo install (or more likely maybe cargo install-update) and don't check crates.io either also see it.
with the release (if you publish it also on GH, as you've done so far) people will also see it in their GH feed (if they look at it), spreading the information even further.
i just stumbled across the announcement by chance and would otherwise have missed it completely.
while the deprecation notice is clearly visible in the README on github it is not visible on crates.io and will thus probably be missed by many (by all appearances on crates.io it's still the correct tool to use). it'd be great if you could release a final v0.30.1 to crates.io just to get the README published there.
optionally you could maybe even print a deprecation notice to STDOUT (or STDERR?) on each application invocation so that those which just update it via
cargo install(or more likely maybecargo install-update) and don't check crates.io either also see it.with the release (if you publish it also on GH, as you've done so far) people will also see it in their GH feed (if they look at it), spreading the information even further.
i just stumbled across the announcement by chance and would otherwise have missed it completely.