neat. This may actually solve for some of the related open issues in this repo. I should be able to publish a new release before the end of this weekend. I'll ping you in this thread when I do

I've just tried using it and for some reason it returns an error:

This is not included in @v0.1.5. You need to use @master for now.

I'm getting this error:

Run softprops/action-gh-release@master
⚠️ Unexpected error fetching GitHub release for tag refs/tags/f-f001ea29f1b9664d928acfddbbd9c76a942e2238: HttpError: Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}
##[error]Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}
##[error]Node run failed with exit code 1

The situation I have is that I'm building multiple releases [stable, beta, dev] in a job, since the repo only contains build scripts. I suspect that you can only update the latest release. Has someone encountered this before?

- name: Upload release asset
      if: steps.release_check.outputs.skip_build != 'true' && github.event_name != 'pull_request'
      uses: softprops/action-gh-release@master
      env:
        GITHUB_TOKEN: ${{ secrets.PERMANENT_GITHUB_TOKEN }}
      with:
        tag_name: f-${{ steps.get_engine_version.outputs.engine_version }}
        name: Flutter ${{ steps.get_engine_version.outputs.engine_version }}
        files: ${{ matrix.config.host_tag }}-${{ matrix.config.tag }}.zip

maybe it was just a glitch in the matrix, having difficulties reproducing this reliably

@dvc94ch I had this today:

##[error]Validation Failed: {"resource":"Release","code":"already_exists","field":"tag_name"}

(I'm also using matrixes) - but on when I ran it again it worked...

I don't remember the solution, but I somehow got it to work or worked around it