Build runner core backport #3521
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes #3514 Add a forwarding implementation of `onLevelChanged` which was added in the `Logger` class. Update upper bound SDK constraint to avoid pub publish warning. Remove `dependency_overrides` section in `pubspec.yaml` since there is a separate overrides file.
|
Thanks for the quick PR @jakemac53 |
natebosch
approved these changes
May 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #3519
Currently, users on the previous flutter SDK (3.7, <6 months old), can't get the latest package:build_runner_core but can get the latest package:logging. This causes compile errors due to a member not being implemented.
This backports the fix to build_runner_core 7.2.7+1, which should be resolvable with build_runner version 2.3.3, which was the last version to allow a Dart version <3.0.0 (it supports 2.14 and later).
Once this is approved, I will tag and release, and then resolve merge conflicts with master so there is a changelog entry.