fix: bump actions to Node.js 24#245
Open
blik616287 wants to merge 2 commits into
Open
Conversation
- Replace `crane pull` with `crane manifest` in validate_content(): pulling full image tarballs caused the validator to hang for 6 hours on large or slow-to-pull images, hitting the GitHub Actions job timeout. crane manifest hits only the registry manifest endpoint, giving the same existence guarantee with no layer download. - Bump actions/checkout v3.6.0 -> v4.2.2 and tj-actions/changed-files v46.0.1 -> v47.0.6 in pack-validation.yml. GitHub forces Node.js 24 on all runners from 2026-06-16; the pinned v3/v46 versions run on Node.js 20 and will break the workflow starting tomorrow.
…-and-node24-actions # Conflicts: # validator/validate-packs.sh
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.
Summary
pack-validation.ymlpinsactions/checkout@v3.6.0andtj-actions/changed-files@v46.0.1, both of which run on Node.js 20. GitHub is forcing Node.js 24 on all runners starting June 16th; these will break the workflow. Bumped toactions/checkout@v4.2.2andtj-actions/changed-files@v47.0.6.What this does NOT fix
security-scans/syft-licenseis stuckIN_PROGRESSon several open PRs with no target URL. That check runs inspectrocloud/bulwark— outside this repo. The runner job appears to have been dispatched but never completed; someone with bulwark access needs to investigate or re-trigger those checks.Test plan