Repository navigation
ci: Pin node version to patch level - #2674
Merged
Merged
Conversation
tylerbenson
approved these changes
Oct 19, 2026
Contributor
Author
|
I was attempting to resolve #2662 and also the renovate error. As such the first thing was to replicate renovate environment to get the same npm & node version. |
thompson-tomo
force-pushed
the
npm_consistency
branch
from
October 20, 2026 00:36
3c5b2be to
4fc69ca
Compare
wpessers
approved these changes
Oct 22, 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.
This pins node at the patch level to increase consistency between renovate, ci and local.