Creating a release from another repo in the same organization just broke

[ospfranco]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Misc

Discussion Details

Hi, we have a complex build pipeline. Were we need to build a core package and then create releases on multiple sub repos (in the same org) using the artifacts from the core package. In order to achieve this, we were using the action-gh-release with a PAT that had the correct permissions.

Suddenly our build pipeline started failing and I'm now getting the following error:

Run softprops/action-gh-release@v2.2.2
👩‍🏭 Creating new GitHub release for tag 5.6.5...
⚠️ GitHub release failed with status: 403
{"message":"Resource not accessible by integration","documentation_url":"https://docs.github.com/rest/releases/releases#create-a-release","status":"403"}
Skip retry — your GitHub token/PAT does not have the required permission to create a release
⚠️ Unexpected error fetching GitHub release for tag refs/tags/5.6.5: HttpError: Resource not accessible by integration - https://docs.github.com/rest/releases/releases#create-a-release
Error: Resource not accessible by integration - https://docs.github.com/rest/releases/releases#create-a-release

I tried creating a fine-grained token in case this was a problem with the tokens being deprecated but still get the same error. Even if the permissions are set to content:write on the org level.

Any ideas if this broke accidentally or if this is an intentional change on Github?

[Yogeshnema2412]

Why are you starting this discussion?
Question

What GitHub Actions topic or product is this about?
Misc

Discussion Details
We recently encountered an issue where our GitHub Actions workflow, which creates a release in a different repository within the same organization, suddenly stopped working. Our setup uses action-gh-release and a PAT with the necessary permissions. This process has worked reliably in the past, but now it fails when attempting to create the release in the sub-repo. We're trying to understand what might have changed or how to fix this while keeping cross-repo release automation intact.

[ospfranco]

It seems the issue is that the GITHUB_TOKEN no longer can create releases between repos in the same organization. I solved my issue by forking action-gh-release and making it so that it reads the token field before the env GITHUB_TOKEN

softprops/action-gh-release@2bdaa59

The PAT token (or fine-grained token) needs to have access to the org repos to publish the contents