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

"Update all" sometimes causes wrong versions to be applied #64

Open
cachapa opened this issue Sep 9, 2023 · 1 comment
Open

"Update all" sometimes causes wrong versions to be applied #64

cachapa opened this issue Sep 9, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@cachapa
Copy link

cachapa commented Sep 9, 2023

The "update all" functionality seems to cause wrong versions to be incorrectly set when packages have similar names.

Example:

path_provider: ^2.0.8
provider: ^6.0.3

Results in:

path_provider: ^6.0.5  # Broken, should be 2.1.1
provider: ^6.0.3       # Not updated, should be 6.0.5

It seems the problem is that the provider version has been applied to path_provider, presumably because both have the word provider in the package name.

@pszklarska
Copy link
Owner

Hey @cachapa thank you for this report! I'll look into this 👍

@pszklarska pszklarska added the bug Something isn't working label Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants