fix(ci): bump nanvix/workflows to v2.0.1 and grant packages: read#160
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the repository’s Nanvix CI GitHub Actions workflow to use nanvix/workflows v2.0.1 and aligns caller permissions with the reusable workflow’s newly required packages: read permission, preventing the workflow startup failure.
Changes:
- Bump
nanvix/workflows/.github/workflows/nanvix-ci.ymlfromv2.0.0tov2.0.1for both scheduled and non-scheduled runs. - Add workflow-level
permissions: packages: readto satisfy the reusable workflow’s top-level permissions. - Remove redundant job-level permissions from
ci-scheduled(now covered by workflow-level permissions).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
nanvix/workflows v2.0.1 added 'packages: read' to its top-level permissions block (commit 48eeaf7) so the reusable workflow can authenticate to ghcr.io for the docker pull retry loop. GitHub Actions enforces that a reusable workflow's effective permissions must be <= the caller job's. Our caller's explicit permissions block omits 'packages', so that scope implicitly defaults to 'none', causing every PR run to fail with startup_failure (zero jobs) the moment the bump moves the ref to @v2.0.1. Also drop the redundant job-level permissions block on ci-scheduled — it duplicated the workflow-level block exactly and added nothing besides maintenance burden.
ppenna
force-pushed
the
fix/grant-packages-read-permission
branch
from
e3c99af to
be2006f
Compare
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.
Stacks two commits, intended to supersede the open
automation/update-nanvix-workflowsPR:[ci] E: Update nanvix workflow refs to v2.0.1— identical to the automation commit.fix(ci): grant packages: read for v2.0.1 reusable workflow— the missing permission grant.Why both in one PR
The bump alone fails immediately with
startup_failure(zero jobs) becausenanvix/workflowsv2.0.1 addedpackages: readto its top-level reusable-workflow permissions (commit 48eeaf7), and GitHub Actions enforces that a reusable workflow's effective permissions cannot exceed the caller job's. Our caller's explicitpermissions:block omitspackages, so it implicitly defaults tonone.This PR cannot be split: applying just the permission grant on default would un-block the automation PR, but pushing to the
automation/**branch is blocked by repository ruleset (only the automation token bypasses).Cleanups included
Drops the redundant job-level
permissions:block onci-scheduled— it duplicated the workflow-level block exactly and added nothing besides maintenance burden.After merge
automation/update-nanvix-workflowsPR (will become a no-op).Update Workflow Refsruns will see default already at@v2.0.1and reportalready up to date.