-
-
Notifications
You must be signed in to change notification settings - Fork 4
Closed
Labels
acceptedThere is consensus among the team that this change meets the criteria for inclusionThere is consensus among the team that this change meets the criteria for inclusion
Description
This issue was prompted by eslint/eslint.org#825 (comment); I extracted the main point from that comment.
Currently, some repositories, such as eslint.org, eslint-github-bot, and code-explorer, perform version updates for engines.node, npm, or .nvmrc.
References:
- chore: update node.js to v20.19.5 - autoclosed eslint.org#825
- chore: update npm to v10.9.4 - autoclosed eslint-github-bot#253
- chore: update node.js to v22.21.1 - autoclosed eslint-github-bot#252
- chore: update node.js to v20.19.5 - autoclosed code-explorer#215
Only the repositories using eslint-app.json5 are affected.
The node and npm versions are used to define the development environment, so personally I think they're not strictly necessary and tend to create clutter. So, I propose not updating node- or npm-related dependencies via Renovate.
Ref: (eslint-app.json5) https://github.com/eslint/workflows/blob/main/.github/renovate/eslint-app.json5
Metadata
Metadata
Assignees
Labels
acceptedThere is consensus among the team that this change meets the criteria for inclusionThere is consensus among the team that this change meets the criteria for inclusion
Type
Projects
Status
Complete