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

Aberta
  • Algo errado?
#4,554 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Refatoração
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
github, javascript, node.js
Domínio
ci-cd, infrastructure

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Jinja
Estrelas
543
Forks
184
Merge médio
4d 6h
PRs com merge (30d)
8

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de nodejs/build

Todas as issues de nodejs/build

Issues semelhantes

Mais issues de DevOps

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.