CitGM backlog
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 50/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, node.js
Research direction
Start with lib/lookup.json, then review the referenced CitGM issues and pull request to verify package support and current test results. Use the Node.js-citgm Jenkins jobs to validate the affected variants; done means lookup.json contains only supported packages that pass, with failing variants represented by skip entries.
Written by the indexing model from the issue text.
Description
In the nodejs/citgm repo there is a backlog of issues raised, PRs submitted, and PRs that have landed, but haven't been released:
citgmsupports"node": "20.x || 22.x || 24.x"missing out Node.js 26.x. Resolved in https://github.com/nodejs/citgm/pull/1116 on Aug 10, 2026. Unreleased.- Multiple packages sourced from archived repos are failing (
JSONStream,leveldown,q,gulp-util&node-sqlite3). Archived repos are by definition unsupported, since it is not possible to report issues or for updates to be released. The removal ofqwas actioned, however the removal is unreleased. See issue https://github.com/nodejs/citgm/issues/1113. - Multiple packages (
@babel/core,clinic,fastify,jest,node-gyp,pino&uuid) are failing in all current variants. See issue https://github.com/nodejs/citgm/issues/1136. - Two additional failures occur when testing under npm@12. See https://github.com/nodejs/citgm/issues/1130.
The list of packages in nodejs/citgm/lib/lookup.json should contain only packages that successfully test in citgm and that are still supported. Any particular variants that do not pass should include skip entries.
Impact
The Jenkins Node.js-citgm jobs are testing packages that always fail. This unnecessarily increases the test duration (last citgm-smoker was 5 hr 57 min). The normal state for citgm-smoker is that it always fails, instead of only failing when there is a regression.
- Dominant language
- JavaScript
- Stars
- 4.4k
- Forks
- 675
- Avg merge
- 22h 29m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nodejs/Release
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Release-agenda
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#145 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dotenvx/dotenv-vscode#139 ·
-
test-change-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
web-platform-tests/interop#1455 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100