Upgrade to Node version 22
Open
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 68
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 10
Description
Since we definitely need this to reduce CVEs as well. We should even go to node 22 in follow up prs https://nodejs.org/en/about/previous-releases#release-schedule
_Originally posted by @juliusvonkohout in https://github.com/kubeflow/kubeflow/issues/7637#issuecomment-2501473279_
Contributor guide
Research direction
The issue names Node.js 22 and links the Node.js release schedule, but it identifies no repository file, test, or entry point. Start by finding where the dashboard declares and uses its Node version, then verify the upgrade across the repository's checks. Done means the project consistently uses Node.js 22 and the relevant checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100