fix(release-pipeline): give the ci job contents: read so publish stops failing - #28
Merged
GoogilyBoogily merged 1 commit intoAug 18, 2026
Conversation
There was a problem hiding this comment.
Pull request overview
This PR fixes the release pipeline’s reusable-workflow invocation by granting the ci job the minimum required GITHUB_TOKEN permission (contents: read) so the called reusable workflow (.github/workflows/ci.yml) can start successfully.
Changes:
- Add a job-level
permissionsblock tojobs.cigrantingcontents: readto satisfy the nested reusable workflow’s requested permissions.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
adrmachado-public
approved these changes
Aug 18, 2026
GoogilyBoogily
deleted the
DTBTWEB-1765-fix-release-pipeline-ci-permissions
branch
August 18, 2026 20:28
This was referenced Aug 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The
cijob inrelease-pipeline.ymlhad nopermissionsblock of its own, so it inherited the workflow's top-levelpermissions: {}default, which iscontents: none. This broke the downstream actionsThis gives the
cijob its owncontents: read, the same waybump-version,publish-npm, andpublish-releasealready declare their own permissions.