chore: updated node to supported 22,24,25#7628
Merged
SamTV12345 merged 9 commits intodevelopfrom Apr 28, 2026
Merged
Conversation
Review Summary by QodoBump minimum Node.js version to 22 and update CI matrix
WalkthroughsDescription• Updated Node.js version matrix from 20, 22, 24 to 22, 24, 25 • Bumped minimum required Node.js version to 22.0.0 • Updated CI/CD workflows across all test and release pipelines • Added changelog entry documenting breaking change Diagramflowchart LR
A["Node 20, 22, 24"] -- "Remove 20, Add 25" --> B["Node 22, 24, 25"]
C["package.json engines"] -- "Update minimum" --> D["Node >= 22.0.0"]
E["CI Workflows"] -- "Update matrix" --> F["All pipelines"]
G["Documentation"] -- "Update requirements" --> H["README.md"]
File Changes1. .github/workflows/backend-tests.yml
|
Code Review by Qodo
1. Node engine bumped to 22
|
![qodo-free-for-open-source-projects[bot]](https://avatars.githubusercontent.com/in/1068000?s=60&v=4){kind=small}
| }, | ||
| "engines": { | ||
| "node": ">=20.0.0" | ||
| "node": ">=22.0.0" |
There was a problem hiding this comment.
1. Node engine bumped to 22 📘 Rule violation ⚙ Maintainability
This PR raises the minimum supported Node.js version from 20 to 22, which is a breaking compatibility change for existing users who are still on Node 20. The change introduces a hard requirement with no compatibility/fallback path, violating the backward-compatibility requirement.
Agent Prompt
## Issue description
The PR introduces a breaking increase of the minimum Node.js requirement to 22 (via `engines.node`), which violates the backward-compatibility requirement unless a compatibility/deprecation strategy is provided.
## Issue Context
Users on Node 20 will be unable to install/run after this change. If dropping Node 20 is intended, provide a compatibility plan (e.g., deprecation period, delayed enforcement, or release strategy that preserves compatibility in this line).
## Fix Focus Areas
- package.json[45-45]
- src/package.json[136-136]
- CHANGELOG.md[1-6]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Member
Author
There was a problem hiding this comment.
Node 20 is end of life. People can update without any problem.
CI Feedback 🧐A test triggered by this PR failed. Here is an AI-generated analysis of the failure:
|
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
1 participant
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.
No description provided.