Upload faling on windows-latest with EBUSY

[lostbean]

I'm using this action to release binaries from a matrix CI workflow building on macOS, linux and windows. The windows job is failing with the following error:
EBUSY: resource busy or locked, lstat 'D:\pagefile.sys'

The other two are working just fine. Is action-gh-release supported on a windows build?

[softprops]

It looks like you are trying to include all files at the root of your file system with/*. This is likely not what you want. You could try a relative path. This should be relative to the working directory of your checkout.

[lostbean]

Thanks for sharing this awesome GH Action @softprops!

Oh that is definitely not what I want. The workflow is defined exactly like this:

    - name: Setup env
      run: |
        echo ::set-env name=OUTPUT_DIR::$(make show-output-dir)
    - name: Release cli
      if: startsWith(github.ref, 'refs/tags/')
      uses: softprops/action-gh-release@v1
      with:
        files: ${{ env.OUTPUT_DIR }}/*
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Where OUTPUT_DIR is the relative path of the output folder. This exact workflow works on macOS and linux. Maybe something related to the use of environment variables being broken in the Windows setup. It seems the variable was properly set:

Could it be the env is not being passed down to the action code? I'm not sure at which point the context ${{ env.OUTPUT_DIR }} is resolved.

[softprops]

Could it be the env is not being passed down to the action code?

That would be my theory. I don't think env gets inherited between steps by default

I'd try some experiments like setting it explicitly

Or adding a debug step in between

with:
      files: ${{ env.OUTPUT_DIR }}/*
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        OUTPUT_DIR: ${{ env.OUTPUT_DIR }}

[softprops]

The docs say it should be available https://help.github.com/en/actions/reference/workflow-commands-for-github-actions#setting-an-environment-variable

Either way I'd run some experiments to see if there's a way to be more explicit and work backwards to implicit