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

Abierto
  • ¿Algo no está bien?
#4,554 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, javascript, node.js
Área
ci-cd, infrastructure

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Jinja
Estrellas
543
Forks
184
Merge medio
4 d 6 h
PR fusionados (30 d)
8

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nodejs/build

Todos los issues de nodejs/build

Issues similares

Más issues de DevOps

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.