Ed Page

@JohnTitor I'd be interested in hearing the rust-semverver perspective on [my earlier comment](https://github.com/rust-lang/cargo/issues/374#issuecomment-1193984670), including what your thoughts are on - Alternative data sources like rustdoc - Expanding the scope to...

> I think this is still an attractive option, since having the full power of the compiler to run queries (like trait and method resolution) can be useful. Agreed. We...

@matklad what are your thoughts on using rust-analyzer (internal or LSP API) as the data source for a cargo-semverver-like tool? In particular - Would it generally be sufficient? - Could...

We talked about this in the cargo team meeting and we are leaning towards automating this, see https://github.com/rust-lang/cargo/issues/374, like with [cargo-crate-api](https://github.com/crate-ci/cargo-crate-api)

See also https://github.com/killercup/cargo-edit/issues/587

When `rust-version` gets added to the registry, we should inform Dependabot people on https://github.com/dependabot/dependabot-core/issues/5423

@mightyiam #9507 is the issue you want to be following. For background, publishing a crate used to be a blocking operation but to speed up crates.io, they made `cargo publish`...

> Could you add some tests like the following? To add, we should make sure we cover all cases, like when the hidden features are activated and deactivated.

`cargo-release` and `cargo-smart-release` support workspace publishes. In the mean time, I'd recommend using them (`cargo-release` focuses on adapting to many workflows while `cargo-smart-release` focuses on making it very smooth to...

Personally, I'm fine with cargo always waiting. `cargo publish` used to always wait but stopped when crates.io changed its behavior. If its configurable, I personally see waiting as a safer...