Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update subosito/flutter-action action to v2 #10

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 7, 2022

Mend Renovate

This PR contains the following updates:

Package Type Update Change
subosito/flutter-action action major v1.5.3 -> v2.16.0

Release Notes

subosito/flutter-action (subosito/flutter-action)

v2.16.0

Compare Source

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

Compare Source

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.

v2.14.0

Compare Source

v2.13.0

Compare Source

v2.12.0

Compare Source

v2.11.0

Compare Source

Allow git ref as version for master channel:

steps:
- uses: actions/checkout@v3
- uses: subosito/flutter-action@v2
  with:
    flutter-version: '5b12b74' # tag, commit or branch
    channel: 'master'
- run: flutter --version

v2.10.0

Compare Source

v2.9.1

Compare Source

v2.9.0

Compare Source

  • Rewrite to make simpler
  • Drop master channel
  • Drop searching for a version with a v-prefix query, use, e.g, 0.11.9 instead of v0.11.9
  • Support restore keys for cache

v2.8.0

Compare Source

v2.7.1

Compare Source

v2.7.0

Compare Source

v2.6.2

Compare Source

v2.6.1

Compare Source

v2.6.0

Compare Source

v2.5.0

Compare Source

v2.4.0

Compare Source

v2.3.0

Compare Source

v2.2.1

Compare Source

quiet unzip

v2.2.0

Compare Source

add cache-path option

v2.1.0

Compare Source

add cache option

v2.0.4

Compare Source

add actions/cache support

v2.0.3

Compare Source

fix PUB_CACHE env

v2.0.2

Compare Source

update v2 readme

v2.0.1

Compare Source

written as shell script


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@codecov
Copy link

codecov bot commented Mar 7, 2022

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.00%. Comparing base (2dd0482) to head (74cc27b).

❗ Current head 74cc27b differs from pull request most recent head 3d658bf. Consider uploading reports for the commit 3d658bf to get more accurate results

Additional details and impacted files
@@          Coverage Diff           @@
##           master     #10   +/-   ##
======================================
  Coverage        0   0.00%           
======================================
  Files           0       1    +1     
  Lines           0       8    +8     
======================================
- Misses          0       8    +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/subosito-flutter-action-2.x branch from 9a8429b to acb7b75 Compare May 16, 2022 01:57
@renovate renovate bot force-pushed the renovate/subosito-flutter-action-2.x branch from acb7b75 to d50c7ca Compare November 20, 2022 08:37
@renovate renovate bot force-pushed the renovate/subosito-flutter-action-2.x branch from d50c7ca to 74cc27b Compare March 23, 2023 13:36
@renovate renovate bot force-pushed the renovate/subosito-flutter-action-2.x branch from 74cc27b to 3796319 Compare October 11, 2023 11:07
@renovate renovate bot force-pushed the renovate/subosito-flutter-action-2.x branch from 3796319 to e440b42 Compare November 1, 2023 13:20
@renovate renovate bot force-pushed the renovate/subosito-flutter-action-2.x branch from e440b42 to 323ff29 Compare March 1, 2024 10:41
@renovate renovate bot force-pushed the renovate/subosito-flutter-action-2.x branch from 323ff29 to 10b1786 Compare March 20, 2024 08:07
@renovate renovate bot force-pushed the renovate/subosito-flutter-action-2.x branch from 10b1786 to 6fa5cef Compare April 1, 2024 04:02
@renovate renovate bot force-pushed the renovate/subosito-flutter-action-2.x branch from 6fa5cef to 3d658bf Compare April 2, 2024 13:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants