ci: declare workflow-level contents: read on lint-docs and openapi-tests#6308
Open
arpitjain099 wants to merge 1 commit into
Open
ci: declare workflow-level contents: read on lint-docs and openapi-tests#6308arpitjain099 wants to merge 1 commit into
contents: read on lint-docs and openapi-tests#6308arpitjain099 wants to merge 1 commit into
Conversation
Both workflows do read-only validation (markdown lint and openapi spec tests). No GitHub API writes from the workflow, so contents: read at the workflow level is the appropriate cap for the default GITHUB_TOKEN. Same post-CVE-2025-30066 supply-chain hardening pattern (tj-actions/changed-files compromise). Other docs workflows that use cache: pnpm or write paths are intentionally untouched. yaml.safe_load validated. Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
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
1 participant
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.
Both workflows do read-only validation (markdown lint, openapi spec tests). No GitHub API writes, so a workflow-level
contents: readis the appropriate cap for the defaultGITHUB_TOKEN.Other workflows in this repo that use
cache: pnpmor have write-needing paths are intentionally untouched, since addingcontents: readthere would break the cache save withoutactions: writeand that scope decision belongs to maintainers.Same hardening shape as the post-CVE-2025-30066 response (
tj-actions/changed-filescompromise). YAML validated locally.