LinwoodDev / Flow

⌚ Feature rich event, group and time managment system
https://docs.flow.linwood.dev
GNU Affero General Public License v3.0
72 stars 5 forks source link

Bump subosito/flutter-action from 2.14.0 to 2.16.0 #53

Closed dependabot[bot] closed 7 months ago

dependabot[bot] commented 7 months ago

Bumps subosito/flutter-action from 2.14.0 to 2.16.0.

Release notes

Sourced from subosito/flutter-action's releases.

v2.16.0

This release introduces the dry-run option, 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: bash

Thank you @​kzrnm for 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-file option (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.yaml

Please 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.

Commits


Dependabot compatibility score

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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)