Error uploading artifact "EISDIR: illegal operation on a directory, read."

Describe the bug When I create a release using the artifacts parameter, the file does not get added to the release and reports the following error for each one:

Failed to upload artifact [filename]. EISDIR: illegal operation on a directory, read. 

To Reproduce My build can be seen here. Not sure if it is specific to using actions/upload-artifact, the job itself is fairly simple:

  release:
    runs-on: ubuntu-latest
    needs:
      - exports
      - exports-macos
    steps:
      - uses: actions/download-artifact@v2
        with:
          path: build/
      - run: |
          version=${GITHUB_REF/refs\/tags\/v/}
          echo "version=${version}" >> $GITHUB_ENV
      - uses: ncipollo/release-action@v1
        with:
          name: Release v${{env.version}}
          tag: ${{env.version}}
          draft: true # for testing
          allowUpdates: true
          artifacts: build/*.zip
          token: ${{ secrets.GITHUB_TOKEN }}

Expected behavior File added to the release

Screenshots Example Github Workflow run

[robpc]

Your theory was completely correct, sorry for polluting this space. Running both with and without the path options results in directories:

4 drwxr-xr-x 2 runner docker 4096 May 21 15:16 maze-test-v0.1.7-osxtest-html.zip
4 drwxr-xr-x 2 runner docker 4096 May 21 15:16 maze-test-v0.1.7-osxtest-linux.zip
4 drwxr-xr-x 2 runner docker 4096 May 21 15:16 maze-test-v0.1.7-osxtest-osx.zip
4 drwxr-xr-x 2 runner docker 4096 May 21 15:16 maze-test-v0.1.7-osxtest-windows.zip

How I read the documentation I thought the no path option would not, but didn’t read close enough. If I find a solution, I’ll update this comment just in case someone stumbles on this issue.

EDIT

Looks like the correct way to do this is with named artifacts, so if you have a matrix and it builds a different filename for each, you can do

      - name: Upload package
        uses: actions/upload-artifact@v2
        with:
          name: build
          path: build/${{ env.package }}

and on the other side

      - uses: actions/download-artifact@v2
        name: build

All the files will then be placed at the root. The documentation says this regarding not using the path option, but was not clear about it needing to use the name

[robpc]

Ahh, thank you for the extra details. I’ll try that.