chore: add flutter version constraint #1376
Open
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.
Checklist:
Update index.md
)I'm using Flutter 3.29 while we are currently using 3.27 in the build process. So I thought we probably should set a constraint and devs would get an error if they use an out-of-range version.
There is a mechanism to set this, but there is currently a bug (flutter/flutter#95472) that makes the project not respect the specified version. (Well, sort of, if does error out if devs use a version lower than the one specified, but still allows a higher version).
This is probably a pointless PR, but I guess we could have this set on our end and hope/wait for the Flutter team to fix the issue?
Ref: https://dart.dev/tools/pub/pubspec#flutter-sdk-constraints