GitHub Actions workflow fails with "Resource not accessible by integration" when trying to create a release

[daniyal-debug]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Hello everyone,

I'm experiencing an issue with GitHub Actions when my workflow attempts to create a GitHub Release.

Environment
GitHub Actions
Ubuntu latest runner
Public GitHub repository
Problem

My workflow successfully checks out the code, installs dependencies, and builds the project. However, it fails during the release step with the following error:

Resource not accessible by integration

The failure only occurs when the workflow tries to create a release or upload release assets.

What I've tried
Verified that the workflow runs on the default branch.
Confirmed that the repository is public.
Regenerated my Personal Access Token and updated the repository secret.
Tried using both the default GITHUB_TOKEN and a Personal Access Token.

Despite these steps, the workflow continues to fail with the same error.

[AbdullahNaseemAbbasi]

The "Resource not accessible by integration" error is most commonly caused by insufficient permissions for the token being used by the workflow.

A few things to check:

Ensure your workflow grants the required permissions. For creating releases, you will typically need:
permissions:
contents: write
If you're using the default GITHUB_TOKEN, verify that the repository's Workflow permissions are configured to allow Read and write permissions instead of read-only.
If the workflow is triggered by a pull request from a fork, be aware that GitHub intentionally restricts the permissions available to the workflow for security reasons. In that case, creating releases or modifying repository contents may not be allowed.
Double-check that any Personal Access Token you're using has the appropriate scopes and that the repository secret references the correct token.

If the problem continues, sharing the relevant part of your workflow YAML (with any sensitive values removed) and the full error log would make it easier for the community to identify the specific permission or configuration issue.