Outdated node-addon-api CI matrix consumes shared runner capacity

Ouverte
#4,554 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Refactorisation
Clarté
Plutôt claire
Activité
Active
Stack technique
github, javascript, node.js

Piste de recherche

Start with the linked parent and child CI jobs and inspect their matrix configuration, version choices, and defaults, then check how the Node.js release schedule is represented in the linked schedule.json. Trace how the child job's Node 24 override selects nightly builds and find the existing validation entry point. Done means the matrix follows supported LTS lines, each phase has an explicit version, choices stay aligned, and validation catches missing supported lines and retained EOL lines.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

The daily node-test-node-addon-api-LTS versions job still runs platform matrices for Node.js 18, 20, 22, and 25. The phase labelled “Test main” inherits the child job's default of 25, as confirmed in this build.

18, 20, and 25 are all EOL, so three of the four phases target unsupported release lines, while supported LTS lines 24 and 26 are missing. Release schedule

Each phase schedules work across shared Linux, macOS, Windows, and AIX workers. The stale matrix therefore creates avoidable demand for runner capacity used by other CI jobs. The job tests node-addon-api main, which now requires Node.js 22 or newer.

The jobs need updating to:

  • Cover 22, 24, and 26, removing the EOL phases.
  • Set an explicit Node.js version for each phase and correct the misleading “Test main” phase.
  • Refresh the child job's version choices/default and remove its stale Node 24 override, which still downloads v24.0.0-nightly builds.
  • Follow the release schedule automatically, adding new LTS lines and dropping EOL lines. Keep the child job's version choices aligned, and add validation that flags missing supported versions or retained EOL versions so this does not depend on annual manual updates.

Related: #4193.

Langage dominant
Jinja
Étoiles
543
Forks
184
Merge moyen
4 j 6 h
PR mergées (30 j)
8

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de nodejs/build

Toutes les issues de nodejs/build

Issues similaires

Plus d'issues DevOps

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.