fix(ci): publish workflow permissions — top-level permissions: {} blocks OIDC#76
Merged
fix(ci): publish workflow permissions — top-level permissions: {} blocks OIDC#76
Conversation
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.
Problem
PR #75 added
permissions: {}at the top level ofpublish.ymlto satisfy CodeQL security warnings. Butpermissions: {}means zero permissions for all jobs — job-levelpermissionscan only narrow the top-level scope, never widen it.This caused a
startup_failureon every tag push since v0.1.43+.Root Cause
GitHub rejects the workflow before it even starts because the job requests more than the workflow allows.
Fix
Set top-level permissions to the minimum needed across all jobs:
Each job still declares its own minimal permissions.
Testing
After merge, re-tag v0.1.48 (or bump to v0.1.49) to trigger a publish.