flutterfire
flutterfire copied to clipboard
chore(deps): bump subosito/flutter-action from 2.12.0 to 2.16.0
Bumps subosito/flutter-action from 2.12.0 to 2.16.0.
Release notes
Sourced from subosito/flutter-action's releases.
v2.16.0
This release introduces the
dry-runoption, which lets you only get action outputs without downloading Flutter. This can be useful if you want to set up some automations to be notified about new Flutter releases.steps: - name: Clone repository - uses: actions/checkout@v4 - name: Set up Flutter uses: subosito/flutter-action@v2 id: flutter-action with: channel: stable dry-run: true - run: | # Always print the latest stable version. echo CHANNEL=${{ steps.flutter-action.outputs.CHANNEL }} echo VERSION=${{ steps.flutter-action.outputs.VERSION }} shell: bashThank you
@​kzrnmfor suggesting and implementing it in #270!v2.15.0
Hi! I'm Bartek and I'm a new maintainer of this action. I promise to take good care of it.
This release introduces the
flutter-version-fileoption (implemented in #290), which lets you easily centralize Flutter version in a single place – your pubspec.yaml file:You can use it like this:
steps: - name: Clone repository uses: actions/checkout@v4 - name: Set up Flutter uses: subosito/flutter-action@v2 with: channel: stable flutter-version-file: pubspec.yaml # path to pubspec.yamlPlease note that for this to work, you need to specify exact Flutter version in pubspec.yaml:
environment: dart: ">=3.3.0 <4.0.0" flutter: 3.19.0 # This must be exact! No ranges allowed.Apart from that, some minor README updates and code cleanup were performed.
... (truncated)
Commits
44ac965Add dry-run (#270)980391amore README fixes (#292)3d80492update README (#291)0ef13f1Addflutter-version-file(#290)7564de3Merge pull request #288 from subosito/chore/action_yaml_refactor2b3ab6cconvert some if-statements to be POSIX-compatible49cd171split longer linescf12a39Merge pull request #287 from subosito/minorcea4cf6workflow.yaml: minor fix043862dMerge pull request #286 from subosito/format- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)