Julien Cretin

You can now merge or rebase this on dev/changelog. You might want to also move changelog.rs to cli-tools too.

With `rustfmt 1.4.22-nightly (97d0301 2020-10-04)` it looks like enabling this option does the opposite of what the documentation says. ```rust enum Foo { X1, // X2, // X3, } ```...

> I have a build script that prints "cargo::warning=Missing ENV variable that is important for release". This i fine during development but I want it to be a compile error...

> * so raising the version requirement above that vulnerable version would run counter to "I want my users to have maximal choice" which I also try to maintain That's...

> Even with `--breaking`. `--breaking` is a "force" flag, not a strategy flag. `cargo update` picks the latest, so a flag that doesn't feels strange (I've had other thoughts for...

> I feel like this runs counter to the mental model of `cargo update`. You are telling it to update, so not updating would be strange, even with a flag....

Thanks for the feedback! I agree this is better addressed with a third-party command, which I hope I'll have time to implement.

> Could you give an idea of what the impact to you is? `cargo publish` prints warnings that are expected and can't be silenced, thus reducing the usefulness of actual...

> `cargo package` transforms your `Cargo.toml` to explicitly list all build-targets. I might be missing something here. It seems like before #13713 (or at least with nightly-2024-05-01) the build-targets are...

I spoke too fast, using `autotests = false` is not a good solution, because it prevents using `cargo test --test=bar`. Actually, if there was a `publish` field in [target configuration](https://doc.rust-lang.org/cargo/reference/cargo-targets.html#configuring-a-target),...