fix(ci): downgrade node due to nodejs/node#53902 #56
Conversation
A bug in node version 22.5.0 has caused the CI to fail. While a patch has been merged, a release is still awaited. This PR works around that by pinning the node version to one that does not contain the bug. Once there is a new release, the pinned part (`.4`) can be removed
WalkthroughThe Node.js version in the GitHub Actions workflow is downgraded from 22 to 22.4 due to a bug present in version 22.5. A comment is added to explain the bug and advise reverting the version once it is resolved. Additionally, a step to clear the npm cache is introduced using Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- .github/workflows/lint.yml (1 hunks)
Additional comments not posted (2)
.github/workflows/lint.yml (2)
31-32: LGTM!Adding the step to clear the npm cache using
npm cache clean --forceis a good practice to prevent issues related to cached packages.
25-29: LGTM! Ensure the Node.js version is correctly set.The comments provide necessary context, and the downgrade to version 22.4 is appropriate given the bug in version 22.5.
However, ensure that the Node.js version is correctly set in the workflow.
Verification successful
Node.js version is correctly set to 22.4 in the workflow.
The comments provide necessary context, and the downgrade to version 22.4 is appropriate given the bug in version 22.5.
.github/workflows/lint.yml:
- Node.js version is set to 22.4.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the Node.js version is correctly set to 22.4 in the workflow. # Test: Search for the Node.js version setting. Expect: Only occurrences of version 22.4. rg --type yaml -A 5 $'node-version: \'22.4\''Length of output: 199
Script:
#!/bin/bash # Description: Verify the Node.js version is correctly set to 22.4 in the workflow. # Test: Search for the Node.js version setting in all YAML files. rg -t yaml -A 5 "node-version: '22.4'"Length of output: 195
Script:
#!/bin/bash # Description: Verify the Node.js version is correctly set to 22.4 in the workflow. # Test: Search for the Node.js version setting across all files. rg -A 5 "node-version: '22.4'"Length of output: 38
Script:
#!/bin/bash # Description: Verify the Node.js version is correctly set to 22.4 in the workflow. # Locate the workflow file and search for the Node.js version setting. fd -e yml | xargs rg -A 5 "node-version: '22.4'"Length of output: 56
Script:
#!/bin/bash # Description: Display the contents of the GitHub Actions workflow file to verify the Node.js version setting. # Display the contents of the .github/workflows/lint.yml file. cat .github/workflows/lint.ymlLength of output: 1311
A bug in node version 22.5.0 has caused the CI to fail. While a patch has been merged, a release is still awaited. This PR works around that by pinning the node version to one that does not contain the bug.
Once there is a new release, the pinned part (
.4) can be removedSummary by CodeRabbit