You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find it a bit annoying that whenever I update Flutter, I have to change the version in pubspec.yaml and in my GitHub Actions workflows.
I think it'd be great if this action would infer Flutter version from pubspec.yaml:
- name: Set up Flutteruses: subosito/flutter-action@v2with:
# channel: stable # not needed - stable would be used by default# flutter-version: '3.7.0' # not needed - would be inferred `pubspec.yaml`architecture: x64cache: true
Which version would you infer from >= 3.5.0 <4.0.0?
The minimum one. It's a good practice to keep the lower bound of flutter version constraint the same as the Flutter version you use. Try to set an upper bound on flutter in a package's pubspec.yaml and after running flutter pub publish --dry-run you'll see:
Package validation found the following potential issue:
* The Flutter constraint should not have an upper bound.
In your pubspec.yaml the constraint is currently `>=3.3.0 <4.0.0`.
You can replace that with just the lower bound: `>=3.3.0`.
See https://dart.dev/go/flutter-upper-bound-deprecation
So for using current stable version of Flutter, it'd be:
At work, when we upgrade a project to a newer Flutter version, we also update lower bound of flutter in pubspec.yaml, and I think it's a good practice.
Repository owner
locked and limited conversation to collaborators
Mar 21, 2023
I find it a bit annoying that whenever I update Flutter, I have to change the version in
pubspec.yaml
and in my GitHub Actions workflows.I think it'd be great if this action would infer Flutter version from
pubspec.yaml
:This approach is used in, for example, the actions/setup-go:
Of course, it'd still be possible to explicitly specify the Flutter version to use.
The text was updated successfully, but these errors were encountered: