Pin GitHub Actions and configure Renovate#33
Merged
Conversation
dannysauer
enabled auto-merge (squash)
July 17, 2026 22:46
eduardoRoth
approved these changes
Jul 17, 2026
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
actions/checkout@v7.0.0andactions/setup-node@v7.0.0commit SHAmajor.minor.patchversion comments so Renovate can follow the associated tagsWhy
Floating major tags can move without a repository change. Full commit SHAs make workflow execution reproducible, while the version comments let Renovate identify and update the corresponding releases.
The
.tool-versionsaddition was moved to PR #32, where the npm publishing workflow consumes it directly.Validation
v7.0.0release tagsactionlint .github/workflows/release-build.yml .github/workflows/validate.ymlprettier --checkfor the changed Renovate and workflow filesrenovate-config-validator .github/renovate.jsonuses:references remain in existing workflows