Ayush SinghandZoltan Kochan b60172e3b0 fix(node-resolver): propagate network errors when reading musl assets (#14854) ...

Only HTTP 404 from unofficial-builds.nodejs.org is ignored when reading the
musl assets of a Node.js release, since that is how the mirror reports a
release it never built. Every other status and every transport error now
aborts the resolve, so a blocked or unreachable mirror can no longer leave
the musl assets out of the lockfile on one machine and not another
pnpm/pnpm#14813.

---------

Co-authored-by: Zoltan Kochan <z@kochan.io>

2026-09-14 16:24:08 +02:00

..

hash

chore(release): 11.27.0 (#14856)

2026-09-12 12:01:04 +02:00

integrity

chore(release): 11.26.0 (#14638)

2026-09-07 01:30:44 +02:00

object-hasher

chore(release): 11.17.0, pacquet 12.0.0-alpha.19, pnpr 0.1.0-alpha.5 (#13237)

2026-07-23 17:07:05 +02:00

shasums-file

fix(node-resolver): propagate network errors when reading musl assets (#14854)

2026-09-14 16:24:08 +02:00