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

Upgrade to use analyzer ^5.0.0 #377

Closed
RoarGronmo opened this issue Oct 16, 2022 · 1 comment
Closed

Upgrade to use analyzer ^5.0.0 #377

RoarGronmo opened this issue Oct 16, 2022 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@RoarGronmo
Copy link

Trying to upgrade dependencies and find that resolving is lacking behind due to chopper using not latest dependency of analyzer. Chopper libraries seems to use analyzer 4.4.0. Other dependecies are using analyzer ^5.0.0.

Because no versions of drift_dev match >=2.2.0 <2.2.0+1 and drift_dev >=2.2.0+1 depends on analyzer ^5.0.0, drift_dev >=2.2.0 requires analyzer ^5.0.0.
And because chopper_generator >=5.0.1 depends on analyzer ^4.4.0, drift_dev >=2.2.0 is incompatible with chopper_generator >=5.0.1.
So, because mwork depends on both chopper_generator ^5.1.0 and drift_dev ^2.2.0, version solving failed.
pub finished with exit code 1

Please upgrade chopper libraries to use analyzer ^5.0.0

@RoarGronmo RoarGronmo added the bug Something isn't working label Oct 16, 2022
@techouse techouse self-assigned this Oct 16, 2022
@techouse
Copy link
Collaborator

techouse commented Oct 16, 2022

I think that bumping it up to ^5.0.0 is a bit harsh because that version removed quite a few deprecated APIs. It would probably also warrant a minor version release rather than just a patch release, so I went with analyzer: '>=4.4.0 <6.0.0' which should give users a gentler transition.

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