Unable to determine Flutter version for channel: stable version: x64 architecture:

[carloshenrique-dev]

I get this issue today, how can I fix it? I did not change the workflow recently.

[joseph-grabinger]

Same here! Unable to determine Flutter version for channel: master version: any architecture: x64
The action worked fine yesterday.

Here is my workflow:

name: Tests

on:
  push:
    branches: [ "main" ]
  pull_request:
    branches: [ "main" ]

jobs:
  tests:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout the code
        uses: actions/checkout@v3

      - name: Clone Flutter repository with master channel
        uses: subosito/flutter-action@v2
        with:
          channel: master
      - run: flutter doctor -v
      - run: flutter pub get

This is my error:

Run subosito/flutter-action@v2
  with:
    channel: master
    flutter-version: any
    cache: false
    cache-key: flutter-:os:-:channel:-:version:-:arch:-:hash:
    cache-path: /opt/hostedtoolcache/flutter/:channel:-:version:-:arch:
    architecture: X64
Run $GITHUB_ACTION_PATH/setup.sh -p -c '/opt/hostedtoolcache/flutter/:channel:-:version:-:arch:' -k 'flutter-:os:-:channel:-:version:-:arch:-:hash:' -n 'any' -a 'X64' master
  $GITHUB_ACTION_PATH/setup.sh -p -c '/opt/hostedtoolcache/flutter/:channel:-:version:-:arch:' -k 'flutter-:os:-:channel:-:version:-:arch:-:hash:' -n 'any' -a 'X64' master
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
Unable to determine Flutter version for channel: master version: any architecture: x64
Error: Process completed with exit code 1.

[matthew-carroll]

Do we know if this is a flutter-action bug or a Flutter bug?

[subosito]

For version 2.9.x, we dropped the support for the master channel. Please update accordingly.

[matthew-carroll]

What do you mean you "dropped the support for the master channel"? We can't run GitHub actions with this tool on master anymore?

[subosito]

Yes, but if you need such functionality feel free to create a PR for that.

[arnemolland]

Dropping support for the master channel is a breaking change, and it just broke all our workflows across multiple repositories. Would you consider reverting that change and rather put it in a v3 tag instead?

[matthew-carroll]

Yes, please do this. Many people have come to depend on this tool and it broke in a major way out of nowhere.

[yurikoles]

No, you.

[arnemolland]

Thanks for adding it back to v2, @subosito 🙌

Out of curiosity, what is the rationale behind dropping master support? I'm not familiar with the complexity of the action.