chore(deps): update actions/checkout and actions/setup-node to v7 - #69
Merged
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
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.
Majors applied
actions/checkoutv6 -> v7 (8 occurrences per repo)actions/setup-nodev6 -> v7 (2 occurrences per repo)Both are digest-pinned with the tag as a trailing comment, and every SHA was resolved through
gh api .../git/refs/tagsrather than copied.Discovery
setup-nodev7 was not an open Renovate PR. It sits in theRate-Limitedsection of the dependency dashboard, so it would have stayed invisible until the limit cleared. Applying it here clears both dashboards.Release notes
actions/checkoutv7.0.0, the only breaking item:Neither trigger is used in this repository, so the change cannot affect it. Verified across all five workflow files.
Verification
GitHub Actions is free on this public repository, so CI proves this directly. Locally the
validatejob was also mirrored step by step:validate_skill.pyreportsSkill is valid.,validate_eval_criteria.pyvalidates 52 scenarios,py_compile,bash -n, JSON and YAML validation all pass. The four "close to runtime references" warnings are pre-existing and unchanged by this diff.