GitHub release failed with status: 403

[donkeyx]

Hey guys,

I am getting a 403 when pushing a release using the action. I have attached the config and a screenshot of my security settings which should be ok. Any help appreciated >

code block <<

      - name: Release with Notes
        uses: softprops/action-gh-release@v1
        if: startsWith(github.ref, 'refs/tags/')
        with:
          draft: false
          generate_release_notes: true
          files: |
            bin/tcp-wait.arm64
            bin/tcp-wait.darwin.amd64
            bin/tcp-wait.linux.amd64
            bin/tcp-wait.windows.amd64
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

error <<

Run softprops/action-gh-release@v1
👩‍🏭 Creating new GitHub release for tag v0.0.1-test...
⚠️ GitHub release failed with status: 403
undefined
retrying... (2 retries remaining)
👩‍🏭 Creating new GitHub release for tag v0.0.1-test...
⚠️ GitHub release failed with status: 403
undefined
retrying... (1 retries remaining)
👩‍🏭 Creating new GitHub release for tag v0.0.1-test...
⚠️ GitHub release failed with status: 403
undefined
retrying... (0 retries remaining)
❌ Too many retries. Aborting...

workflow permissions <<

[muellerk22]

I'm getting the same 403

Run softprops/action-gh-release@v1
👩‍🏭 Creating new GitHub release for tag v0.0.11...
⚠️ GitHub release failed with status: 403
undefined
retrying... (2 retries remaining)
👩‍🏭 Creating new GitHub release for tag v0.0.[11](https://github.com/Cloudzero/amazon-cloudwatch-agent/runs/6749363256?check_suite_focus=true#step:16:12)...
⚠️ GitHub release failed with status: 403
undefined
retrying... (1 retries remaining)
👩‍🏭 Creating new GitHub release for tag v0.0.11...
⚠️ GitHub release failed with status: 403
undefined
retrying... (0 retries remaining)
❌ Too many retries. Aborting...
Error: Too many retries.

      - name: Release
        if: ${{ github.ref == 'refs/heads/cloudzero-optimized' }}
        uses: softprops/action-gh-release@v1
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          name: V${{ env.NEXT_TAG }}
          tag_name: v${{ env.NEXT_TAG }}

I have the same workflow permissions too.

[ArjanJ]

I resolved this by adding this to my yml workflow file

permissions:
  contents: write

[raviqqe]

You might also need to disable tag protection rules in your repository if any are defined.

[sumanthkumarc]

#236 (comment) worked for me.

[Timmmm]

Worth adding this to the readme surely?

[HinTak]

I resolved this by adding this to my yml workflow file

permissions:
  contents: write

would it make sense to include this snipplet in the examples in the top-level README, instead of / in addition of mentioning it at the end? I suppose most people are as lazy as me and just leave the default repository permission alone, copy-and-paste the example and edit a bit to try to get it to work. So it would be nice to have the examples working as-is in most people/organizations' settings.

If the repository-level change is preferred, it probably should be mentioned at the top of the readme, instead of the end. I think having it as a per-job/per-action setting is fine for most people.

[ajithkumar-natarajan]

I had to enable this setting at my organization level

[donkeyx]

this was resolved with the settings provided by @HinTak <<
permissions:
contents: write
packages: write