Sergey "Shnatsel" Davidoff

The error message missing a "not" originates from the `gix` crate, and the message seems to be cut off also due to `gix` behavior. I have filed an issue upstream:...

@kpreid could you please try https://github.com/rustsec/rustsec/issues/1053 and post the error it produced? It should be more informative this time around.

Is that macro really public? [It certainly does not appear in documentation](https://docs.rs/rustsec/latest/rustsec/?search=format_err). I don't see a `pub` or `#[macro_export]` on its definition either. So changing this macro should not be...

I think we'll need to rework (and semver-break) the `rustsec::Error` type and likely ditch or rework `format_err!` too. We have these requirements: 1. Preserve information of the original error (like...

Oh, since the fields are private that's not even going to be semver-breaking. Yes, I'd love to have such a PR!

Yeah. My fault. I was aware of that, but didn't want to change it so that different versions don't try to coordinate using different lockfiles and trample over each other...

Certain other standards for vulnerability information interchange exist. For example CycloneDX added vulnerability data in v1.4. There are also VEX standards. Is there a particular reason to prefer SARIF over...

This is something to take care of in https://github.com/rustsec/rustsec/issues/938

I think we can just exclude it from the workspace, or bump MSRV if necessary because 1.40 is ancient by now.

Thank you! I admit I am confused by the [documentation](https://axodotdev.github.io/cargo-dist/book/reference/config.html#dispatch-releases) of `dispatch-releases` option. Specifically, I do not understand how do I trigger it. Is it the usual "Actions > Release...