Artifacts are uploaded after the GH Release published event is triggered

[carlosperate]

When creating a GH Release with files to upload as artifacts, the GH Release is published before the file uploads are done.

This means that any workflow triggered from a GH Release being "published", will start running before all the artifacts are availble in the release.

on:
  release:
    types: published

jobs:
  download-release-artifacts:
    runs-on: ubuntu-latest
    steps:
      - name: Set the GH Release tag to step output
        id: get_tag
        shell: bash
        run: echo "tag=${GITHUB_REF#refs/*/}" >> $GITHUB_OUTPUT
      # At this point the GH release artifacts might not have been completely uploaded by ncipollo/release-action
      - name: Download GH Release artifacts
        shell: bash
        run: gh release download ${{ steps.get_tag.outputs.tag }} --repo ${{ github.server_url }}/${{ github.repository }}
        env:
          GH_TOKEN: ${{ github.token }}

[ncipollo]

The release need to exist before you can upload assets to it. See https://docs.github.com/en/rest/releases/assets?apiVersion=2022-11-28#upload-a-release-asset

You can maybe try creating a draft release (not sure if that triggers the publish event or not, if it does you could maybe filter out draft releases).

[carlosperate]

For a workaround I'll likely just add a hacky wait/delay in my project.
Would it make sense for this action to create first a draft release, to be able to add the artifacts, and then publish it?
I guess there might be more events fired at that point, so not sure if that's better or worse for the default behaviour.

[ncipollo]

Yeah I'd be worried that would generate more events, and is even less atomic than it is now (if something breaks in the middle of that users would be left with a seemingly random draft release).

I think you can achieve something similar though by chaining two release actions together, the first is a draft with artifacts, the second updates it to non-draft.