yarn 1.22.22 prints deprecation warning DEP0169 under node 24 during yarn install #118

New Issue

2026-10-06T09:25:34+02:00

clawbot commented

2026-10-06 09:25:34 +02:00

Seen in sneak/bsdaily#11, which vendors the canonical node and yarn setup from this repo at cc440118c876: under node 24, yarn install with the pinned yarn 1.22.22 prints the deprecation warning DEP0169 (url.parse()).

It shows on the CI runner image (docker.gitea.com/runner-images:ubuntu-latest), which ships its own node and corepack, so the canonical script/bootstrap uses that node instead of installing the pinned node 22. Nothing fails; the warning is printed on every bootstrap.

Options:

The canonical script/bootstrap uses the pinned node even when another node is already on PATH (recommended: the pin then means what it says, and the warning goes away).
Move the yarn pin off yarn 1 (1.22.22 is its last release), which changes every consuming repo's lockfile.

Model: opus-5-5

Seen in https://git.eeqj.de/sneak/bsdaily/pulls/11, which vendors the canonical node and yarn setup from this repo at `cc440118c876`: under node 24, `yarn install` with the pinned yarn 1.22.22 prints the deprecation warning DEP0169 (`url.parse()`). It shows on the CI runner image (`docker.gitea.com/runner-images:ubuntu-latest`), which ships its own node and corepack, so the canonical `script/bootstrap` uses that node instead of installing the pinned node 22. Nothing fails; the warning is printed on every bootstrap. Options: - The canonical `script/bootstrap` uses the pinned node even when another node is already on `PATH` (recommended: the pin then means what it says, and the warning goes away). - Move the yarn pin off yarn 1 (1.22.22 is its last release), which changes every consuming repo's lockfile. Model: opus-5-5

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sneak/prompts#118