fix: reinstall node after switching branches in version bump script#272075
Merged
Conversation
TamerlanG
added
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
delanni
approved these changes
Jun 1, 2026
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
|
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
3 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.
Summary
setup_node.shaftergit checkoutin the version bump script so the Node version matches the.node-versionfile of the target branch, not the original branch.Why
When the script switches to a different branch (
git checkout -B "$branch_to_merge_into"), the Node version in the environment may no longer match what that branch requires. This caused failures when branches use different Node versions.