You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cloning the repo and running local tests using Ubuntu 26.04.1 LTS and running under Node.js 22, 24 & 26 confirm the compatibility issues for Node.js 24 & 26.
This appears to be an issue with the snapshots saved in the test-tap/reporters/tap.edgecases.v*.log of https://github.com/avajs/ava which refer to line numbers that have changed within the Node.js release line updates, for instance between Node.js 26.4.0 and Node.js 26.5.0.
This could be fixed by just re-recording the snapshots so they correspond to the latest Node.js releases for each supported release line. That would however make the test fail on earlier releases of the same release line.
$ citgm avainfo: starting | avainfo: lookup | avainfo: lookup-found | avainfo: ava lookup-replace | github:avajs/ava/archive/v8.0.2.tar.gzinfo: ava npm: | Downloading project: github:avajs/ava/archive/v8.0.2.tar.gzerror: failure | Failure getting project from npmerror: | npm error code 128error: | npm error An unknown git error occurrederror: | npm error command git --no-replace-objects ls-remote ssh://git@github.com/avajs/ava/archive/v8.0.2.tar.gz.giterror: | npm error Warning: Permanently added 'github.com' (ED25519) to the list of known hosts.error: | npm error git@github.com: Permission denied (publickey).error: | npm error fatal: Could not read from remote repository.error: | npm errorerror: | npm error Please make sure you have the correct access rightserror: | npm error and the repository exists.error: | npm error A complete log of this run can be found in: C:\Users\mikem\AppData\Local\npm-cache\_logs\2026-10-15T19_19_40_730Z-debug-0.logerror: failing module(s) |error: module name: | avaerror: version: | 8.0.2error: error: | Failure getting project from npmerror: | npm error code 128error: | npm error An unknown git error occurrederror: | npm error command git --no-replace-objects ls-remote ssh://git@github.com/avajs/ava/archive/v8.0.2.tar.gz.giterror: | npm error Warning: Permanently added 'github.com' (ED25519) to the list of known hosts.error: | npm error git@github.com: Permission denied (publickey).error: | npm error fatal: Could not read from remote repository.error: | npm errorerror: | npm error Please make sure you have the correct access rightserror: | npm error and the repository exists.error: | npm error A complete log of this run can be found in: C:\Users\mikem\AppData\Local\npm-cache\_logs\2026-10-15T19_19_40_730Z-debug-0.logerror: error: | undefinederror: done | The smoke test has failed.info: duration | test duration: 3416ms
Activity
MikeMcC399 commentedon Oct 5, 2026
Suggestion
>=24to citgm lookup to block testing on incompatible Node.js release lines (retain current skips)MikeMcC399 commentedon Oct 8, 2026
CI workflow is https://github.com/avajs/ava/blob/main/.github/workflows/ci.yml
https://github.com/avajs/ava/actions/runs/26000541390 last tested on May 17, 2026.
Logs are no longer available.
Current Node.js 26.x at that time was Node.js 26.1.0
citgm avaresultA test regression appears with Node.js 26.5.0, released 2026-07-08.
nodejs/node#64329 (comment) noted multiple regressions in CITGM with the Node.js 26.5.0 release, including
ava-v8.0.0.MikeMcC399 commentedon Oct 8, 2026
This appears to be an issue with the snapshots saved in the
test-tap/reporters/tap.edgecases.v*.logof https://github.com/avajs/ava which refer to line numbers that have changed within the Node.js release line updates, for instance between Node.js 26.4.0 and Node.js 26.5.0.This could be fixed by just re-recording the snapshots so they correspond to the latest Node.js releases for each supported release line. That would however make the test fail on earlier releases of the same release line.
cc: @sindresorhus @novemberborn
novemberborn commentedon Oct 8, 2026
That's now fixed in
mainbut there's an unrelated CI failure which stops me from releasing.novemberborn commentedon Oct 15, 2026
8.0.2 is now out.
MikeMcC399 commentedon Oct 15, 2026
@novemberborn
The repo change in 8.0.2 is causing issues:
MikeMcC399 commentedon Oct 15, 2026
It looks like you've switched from npm to pnpm as package manager. I didn't notice that at first, since it's not specifically listed in https://github.com/avajs/ava/releases/tag/v8.0.2 unless you drill down into avajs/ava#3496
novemberborn commentedon Oct 16, 2026
Correct. It's not listed since it doesn't affect end users but makes sense that CITGM has to clone the repo.
MikeMcC399 commentedon Oct 17, 2026
#1195 covers the download failure due to the use of a short-cut
repositorydefinition.novemberborn commentedon Oct 22, 2026
I've published 8.1.1 with pnpm@12.15.
MikeMcC399 commentedon Oct 23, 2026
ava@8.1.2 has fixed the download issue by normalizing the repository key in package.json
The remaining issue is for citgm to migrate ava testing to pnpm, for which I will shortly submit a PR.