Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only ban multiple versions of user-facing dependencies #497

Closed
epage opened this issue Mar 23, 2023 · 1 comment · Fixed by #557
Closed

Only ban multiple versions of user-facing dependencies #497

epage opened this issue Mar 23, 2023 · 1 comment · Fixed by #557
Labels
enhancement New feature or request

Comments

@epage
Copy link
Contributor

epage commented Mar 23, 2023

Is your feature request related to a problem? Please describe.
It can be hard to avoid multiple-versions. In particular for dev-dependencies as they tend to sprawl out more than normal/build dependencies (e.g. criterion) yet they are a lower priority. Not many people will care if clap has duplicate depednencies for local development but they will care when depending on clap.

Describe the solution you'd like
Allow configuring multiple-versions = "deny" to only deny when there are multiple within normal/build dependencies

Describe alternatives you've considered

Additional context

Granted, this won't help with is-terminal as a normal dependency since it pulls in two different versions of windows-sys.

@epage epage added the enhancement New feature or request label Mar 23, 2023
@jaskij
Copy link

jaskij commented Jul 3, 2023

Edge case: there are some crates, like build-info which, afaik, need to have the same version as both dependencies and dev-dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants