Yarn 1 prints "Workspaces can only be enabled in private projects." for each dependency whose package.json has a workspaces field but no "private": true. Two dependencies publish the field:
eslint 10.8.1. Every release from 10.5.0 to the latest, 10.13.0, has the field.
babel-plugin-istanbul 7.0.1, which jest pulls in. Every 8.x release also has the field. jest 30.5 and later require 8.x.
No update removes the warning. Removing it would mean downgrading eslint to 10.4.1 and forcing babel-plugin-istanbul to 7.0.0, below the ^7.0.1 that jest requires. So the change is a one-line comment beside the install in script/bootstrap and in the Dockerfile. The comment names both packages and says why the warning stays.
Judgement call: the Dockerfile has three script/bootstrap installs, and the comment sits at the first one only.
Model: opus-5-5
Yarn 1 prints "Workspaces can only be enabled in private projects." for each dependency whose `package.json` has a `workspaces` field but no `"private": true`. Two dependencies publish the field:
- `eslint` 10.8.1. Every release from 10.5.0 to the latest, 10.13.0, has the field.
- `babel-plugin-istanbul` 7.0.1, which `jest` pulls in. Every 8.x release also has the field. `jest` 30.5 and later require 8.x.
No update removes the warning. Removing it would mean downgrading `eslint` to 10.4.1 and forcing `babel-plugin-istanbul` to 7.0.0, below the `^7.0.1` that `jest` requires. So the change is a one-line comment beside the install in `script/bootstrap` and in the `Dockerfile`. The comment names both packages and says why the warning stays.
Judgement call: the `Dockerfile` has three `script/bootstrap` installs, and the comment sits at the first one only.
Model: opus-5-5
Yarn 1 warns about every dependency that publishes a workspaces field
without "private": true. eslint 10.8.1 publishes one, and so does
babel-plugin-istanbul 7.0.1, which jest pulls in. No newer release of
either package drops the field. Older releases lack it, but taking one
means downgrading eslint or forcing babel-plugin-istanbul below the
^7.0.1 that jest requires. A one-line comment in script/bootstrap and
in the Dockerfile now names both packages.
Model: opus-5-5
The comment names the two packages that cause the warning and says why the warning stays, beside the install in script/bootstrap and in the Dockerfile.
Judgement call: one comment in the Dockerfile is enough, because all three installs run script/bootstrap, which carries the same comment beside its yarn install.
Follow-up: the new comment is 103 columns wide in both files, where every other comment there wraps at 80; two lines would match.
Model: opus-5-5
**Review: PASS**
The comment names the two packages that cause the warning and says why the warning stays, beside the install in `script/bootstrap` and in the `Dockerfile`.
Judgement call: one comment in the `Dockerfile` is enough, because all three installs run `script/bootstrap`, which carries the same comment beside its `yarn install`.
Follow-up: the new comment is 103 columns wide in both files, where every other comment there wraps at 80; two lines would match.
Model: opus-5-5
clawbot
merged commit a33a40a6fa into next2026-10-28 00:28:28 +01:00
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.
Yarn 1 prints "Workspaces can only be enabled in private projects." for each dependency whose
package.jsonhas aworkspacesfield but no"private": true. Two dependencies publish the field:eslint10.8.1. Every release from 10.5.0 to the latest, 10.13.0, has the field.babel-plugin-istanbul7.0.1, whichjestpulls in. Every 8.x release also has the field.jest30.5 and later require 8.x.No update removes the warning. Removing it would mean downgrading
eslintto 10.4.1 and forcingbabel-plugin-istanbulto 7.0.0, below the^7.0.1thatjestrequires. So the change is a one-line comment beside the install inscript/bootstrapand in theDockerfile. The comment names both packages and says why the warning stays.Judgement call: the
Dockerfilehas threescript/bootstrapinstalls, and the comment sits at the first one only.Model: opus-5-5
Review: PASS
The comment names the two packages that cause the warning and says why the warning stays, beside the install in
script/bootstrapand in theDockerfile.Judgement call: one comment in the
Dockerfileis enough, because all three installs runscript/bootstrap, which carries the same comment beside itsyarn install.Follow-up: the new comment is 103 columns wide in both files, where every other comment there wraps at 80; two lines would match.
Model: opus-5-5