chore: Add flutter version constraint to pubspec #583
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
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.
I had version 3.24.5 installed and after updating to the latest head I started getting problems on build.
One of them was:
Which is odd because before updating it just worked.
After some time I noticed that the futter submodule had been updated to version 3.27.
After installing version 3.27.x of the flutter SDK everything started building again.
To not have this happen in the future it's best if we keep the necessary flutter version in the pubspec to get a better error in the future.
The only chore now is that when updating the flutter submodule the pubspec must also be updated.