-
Notifications
You must be signed in to change notification settings - Fork 19
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 analyzer constraint #117
Conversation
Security InsightsNo security relevant content was detected by automated scans. Action Items
Questions or Comments? Reach out on Slack: #support-infosec. |
@Attempt3035 Approach seems fine, looking at the changelog for v6 there's nothing that should effect dependency_validator, and we should catch any issues from the existing unit tests within the repo (we run on both dart 2 and 3) CI failures are unrelated to this change, and were fixed here: #120, If you just merge master on this pr, we can re-run CI and get this merged! Thanks for putting the PR up! |
QA +1
🚀 @Workiva/release-management-p 🚢 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 from RM
Motivation
I noticed analyzer was being resolved to a lower version than available, it's causing warnings in the build runner for freezed.
Changes
I opened the depended-on analyzer versions to include the 6.#.# major release, but less than 7.#.# (Not out yet anyway)
Testing/QA Instructions
I have no idea the implications this may have, and have not looked around this code base. From my testing, everything is operating normally as far as I can see, but this would need a maintainer to run some tests to confirm. I checked the changes in the analyzer package version notes, they seem minimal and I'm guessing won't affect anything with this package :)