Fix CI: bump setup-node to Node 22 for danger-js install - #665
Merged
f-meloni merged 2 commits intoAug 22, 2026
Merged
Conversation
yarn global add danger installs the latest danger-js, whose content-type dependency now requires Node >=22. Every CI job still installed Node 20 via setup-node, so every job failed at the 'Install danger-js' step.
f-meloni
approved these changes
Aug 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
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.
Summary
yarn global add danger) with:content-type@3.0.0: The engine "node" is incompatible with this module. Expected version ">=22". Got "20.20.2"yarn global add dangeralways resolves the latestdanger-js, and itscontent-typedependency now requires Node >=22, but every job installs Node 20 viasetup-nodesetup-nodeto Node 22 across all 5 CI job definitions to matchTest plan