Bump CI actions to v5 and add an npm badge - #12
Merged
Conversation
actions/checkout and actions/setup-node move from v4 to v5, clearing the warning GitHub prints on every run because v4 targets the deprecated Node 20 runtime. This also matches release.yml, so both workflows now pin the same majors. The README gains an npm version badge, now that the package is published. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJR2DDBimsijgYgZS3bUS8
Merged
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
2 participants
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.
Two small follow-ups from #11.
CI actions to v5
actions/checkoutandactions/setup-nodemove from@v4to@v5, in both jobs. GitHub currently prints this on every run:That warning goes away, and
ci.ymlnow matchesrelease.yml, which #11 introduced on v5 — so the deliberate inconsistency I flagged there is resolved. Both workflows pin the same majors:npm badge
The README gains a version badge next to the CI one, now that the package is live:
One caveat worth stating plainly: I could not render-test the badge.
img.shields.iois blocked by this environment's network policy, so the request fails outright from here. What I did verify is the data behind it —registry.npmjs.org/shadowtoolsreturns4.0.0aslatest— and the URL follows shields.io's standardnpm/v/<package>form. If it renders blank, that is where to look.Testing
Both workflows parse, 62 tests pass, and the action versions are consistent across the two files. The real check on the
@v5bump is this PR's own CI run, since it exercises the bumped actions directly — worth confirming the deprecation warning is gone from the log.Generated by Claude Code