Skip to content

ci(release): grant contents:write to the publish job - #24

Merged
andrescera merged 1 commit into
mainfrom
fix/publish-release-perms
Jun 12, 2026
Merged

ci(release): grant contents:write to the publish job#24
andrescera merged 1 commit into
mainfrom
fix/publish-release-perms

Conversation

@andrescera

Copy link
Copy Markdown
Member

What

Add permissions: contents: write to the sign-and-publish job.

Why

Create GitHub Release failed with 403 Resource not accessible by integration. The workflow declares no permissions: block, so GITHUB_TOKEN inherits the repo's read-only default and cannot create a release/tag. Scoping contents: write to the single job that needs it (least privilege) lets softprops/action-gh-release publish the tag + release. CI-only; no src//binary impact.

How to verify

Dispatch Publish Release (stable); Create GitHub Release publishes v2026.6.0 with the .deb + checksum assets.

Risks

Minimal — write scope is limited to the publish job; all other jobs keep default (read) permissions.

Create GitHub Release failed with 403 "Resource not accessible by
integration" because the workflow has no permissions block and inherits
the repo's read-only default GITHUB_TOKEN. Scope contents:write to the
sign-and-publish job (least privilege) so softprops/action-gh-release can
create the tag and release.

How to verify: dispatch Publish Release (stable); Create GitHub Release
publishes v2026.6.0 with the .deb + checksum assets.
@andrescera
andrescera merged commit 7079175 into main Jun 12, 2026
4 checks passed
@andrescera
andrescera deleted the fix/publish-release-perms branch June 12, 2026 11:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant