Is your feature request related to a problem? Please describe.
When working on a feature that requires updates to multiple related crates (that are not part of a single workspace), it's often necessary to create prereleases of crates earlier in the dependency chain and depend on those prerelease in subsequent crates.
It's easy to forget to update the depedent crates to the released versions of the dependency crates once those releases are available.
One might also want to be alerted if a dependency transitively depends on a prerelease.
Describe the solution you'd like
An optional ban configuration for prereleases. I imagine this could be something like prereleases = "allow|warn|deny", just like wildcards, multiple-versions, and the default-feature checks.
Describe alternatives you've considered
A more flexible feature might be something like a regex for what prerelease tags are or are not permitted, but that seems like extreme overkill to me.
Is your feature request related to a problem? Please describe.
When working on a feature that requires updates to multiple related crates (that are not part of a single workspace), it's often necessary to create prereleases of crates earlier in the dependency chain and depend on those prerelease in subsequent crates.
It's easy to forget to update the depedent crates to the released versions of the dependency crates once those releases are available.
One might also want to be alerted if a dependency transitively depends on a prerelease.
Describe the solution you'd like
An optional
banconfiguration for prereleases. I imagine this could be something likeprereleases = "allow|warn|deny", just likewildcards,multiple-versions, and the default-feature checks.Describe alternatives you've considered
A more flexible feature might be something like a regex for what prerelease tags are or are not permitted, but that seems like extreme overkill to me.