[Dart 2 - 2.x stable] Update analyzer version range #363
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Upper bounds of the
analyzer
version need to be increased so that we aren't prevented from pulling newer versions of packages (e.g.,build_web_compilers
) that depend on newer versions ofanalyzer
.Changes
Analyzer
dependency.Release Notes
analyzer
dependency upper bound to ensure the package can consume the latest version of other dependencies.Review
See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.
Please review:
@aaronlademann-wf @greglittlefield-wf @kealjones-wk @sydneyjodon-wk
QA Checklist
Steps from PR author:
analyzer
can resolve to0.38.5
and there are no static errors.0.38.5
and there are no static errors.Anything falling under manual testing criteria outlined in CONTRIBUTING.md
Merge Checklist
While we perform many automated checks before auto-merging, some manual checks are needed: