Mixing specific versions and channels is kinda unergonomic

[benthillerkus]

I often want to write strategies like so

strategy:
  matrix:
    flutter: [3.29.3, 3.32.0, dev, master]

But because of the segmentation of the version into channel and flutter-version I cannot easily just write

- uses: subosito/flutter-action@v2
  with:
    flutter-version: ${{ matrix.flutter }}

Currently I'm doing

- uses: subosito/flutter-action@v2
  if: ${{ matrix.flutter }} != 'dev' && ${{ matrix.flutter }} != 'master'
  with:
    flutter-version: ${{ matrix.flutter }}
    cache: true

- uses: subosito/flutter-action@v2
  if: ${{ matrix.flutter }} == 'dev' || ${{ matrix.flutter }} == 'master'
  with:
    channel: ${{ matrix.flutter }}
    cache: false

But I'd rather not have to

[RyanCarrier]

You are mixing stable channel versions with latest versions of other channels, it makes sense you would have to specify otherwise.
You can use include to get what you want anyway though

strategy:
  matrix:
    include:
      - flutter-version: 3.29.3
        flutter-channel: stable
      - flutter-version: 3.32.0
        flutter-channel: stable
      - flutter-channel: master
      - flutter-channel: dev
    

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/running-variations-of-jobs-in-a-workflow#example-adding-configurations