Every yarn install --frozen-lockfile in Dockerfile (the frontend-lint and frontend stages, and the test stage once #115 lands) prints warning Workspaces can only be enabled in private projects. three times while linking dependencies. package.json declares no workspaces, so the warning comes from the package.json of one or more installed packages, which yarn 1 checks as it links them.
Definition of done:
The packages that cause the warning are named on this issue.
The warning is gone from script/cibuild's output, by updating or replacing what causes it within the pinning rules of REPO_POLICIES.md; or, if nothing in netwatch can remove it, this issue says why and is closed with no change.
One reviewed PR against next if anything changes.
Model: opus-5-5
Every `yarn install --frozen-lockfile` in `Dockerfile` (the `frontend-lint` and `frontend` stages, and the test stage once https://git.eeqj.de/sneak/netwatch/pulls/115 lands) prints `warning Workspaces can only be enabled in private projects.` three times while linking dependencies. `package.json` declares no workspaces, so the warning comes from the `package.json` of one or more installed packages, which yarn 1 checks as it links them.
Definition of done:
- The packages that cause the warning are named on this issue.
- The warning is gone from `script/cibuild`'s output, by updating or replacing what causes it within the pinning rules of `REPO_POLICIES.md`; or, if nothing in netwatch can remove it, this issue says why and is closed with no change.
- One reviewed PR against `next` if anything changes.
Model: opus-5-5
clawbot
self-assigned this 2026-10-07 12:42:16 +02:00
The warning comes from one package, eslint 10.12.0, which the frontend-lint stage installs to lint the frontend. Since 10.5.0 its published package.json declares "workspaces": ["packages/*"] without "private": true, and yarn 1 warns about that. All three warnings come from it. No other installed package has the field, and an install with eslint 10.4.1, the last release without it, prints no warning.
It stays because 10.12.0 is the newest eslint and package.json asks for ^10.12.0. Removing the warning would mean going back to 10.4.1, a linter ten releases and four months older, which would change the lint check netwatch runs. The warning goes away by itself if a later eslint stops publishing the field. No change made.
Judgement call: I counted the downgrade to 10.4.1 as changing what netwatch does, so I did not make it.
Model: opus-5-5
The warning comes from one package, `eslint` 10.12.0, which the `frontend-lint` stage installs to lint the frontend. Since 10.5.0 its published `package.json` declares `"workspaces": ["packages/*"]` without `"private": true`, and yarn 1 warns about that. All three warnings come from it. No other installed package has the field, and an install with `eslint` 10.4.1, the last release without it, prints no warning.
It stays because 10.12.0 is the newest `eslint` and `package.json` asks for `^10.12.0`. Removing the warning would mean going back to 10.4.1, a linter ten releases and four months older, which would change the lint check netwatch runs. The warning goes away by itself if a later `eslint` stops publishing the field. No change made.
Judgement call: I counted the downgrade to 10.4.1 as changing what netwatch does, so I did not make it.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Every
yarn install --frozen-lockfileinDockerfile(thefrontend-lintandfrontendstages, and the test stage once #115 lands) printswarning Workspaces can only be enabled in private projects.three times while linking dependencies.package.jsondeclares no workspaces, so the warning comes from thepackage.jsonof one or more installed packages, which yarn 1 checks as it links them.Definition of done:
script/cibuild's output, by updating or replacing what causes it within the pinning rules ofREPO_POLICIES.md; or, if nothing in netwatch can remove it, this issue says why and is closed with no change.nextif anything changes.Model: opus-5-5
The warning comes from one package,
eslint10.12.0, which thefrontend-lintstage installs to lint the frontend. Since 10.5.0 its publishedpackage.jsondeclares"workspaces": ["packages/*"]without"private": true, and yarn 1 warns about that. All three warnings come from it. No other installed package has the field, and an install witheslint10.4.1, the last release without it, prints no warning.It stays because 10.12.0 is the newest
eslintandpackage.jsonasks for^10.12.0. Removing the warning would mean going back to 10.4.1, a linter ten releases and four months older, which would change the lint check netwatch runs. The warning goes away by itself if a latereslintstops publishing the field. No change made.Judgement call: I counted the downgrade to 10.4.1 as changing what netwatch does, so I did not make it.
Model: opus-5-5