[rush] Rush adds `globalOnlyBuiltDependencies` to my pnpm-config and then subsequently complains about it

[kgetz-arista]

Summary

Rush prompts me to run rush-pnpm --subspace default approve-builds, which adds globalOnlyBuiltDependencies to my pnpm-config file. When I subsequently open that file in vscode, I get a warning on that property: Property globalOnlyBuiltDependencies is not allowed.

It seems that maybe the schema file (https://developer.microsoft.com/json-schemas/rush/v5/pnpm-config.schema.json) hasn't been updated?

Repro steps

1. Upgrade to Rush 5.169.3 and pnpm 10.30.3
2. Run rush update
3. Run rush-pnpm --subspace default approve-builds and approve all of the dependencies
4. Open common/config/rush/pnpm-config.json in vscode

Details

Standard questions

Please answer these questions to help us investigate your issue more quickly:

Question	Answer
@microsoft/rush globally installed version?	5.169.3
rushVersion from rush.json?	5.169.3
pnpmVersion, npmVersion, or yarnVersion from rush.json?	10.30.3
(if pnpm) useWorkspaces from pnpm-config.json?	true
Operating system?	Windows 11
Would you consider contributing a PR?	No
Node.js version (node -v)?	24.12.0

[tluma]

Hey kgetz‑arista! 👋 Based on the Rush documentation, globalOnlyBuiltDependencies is a supported PNPM option – it’s documented in the PnpmOptionsConfiguration API as an allow‑list for packages that are allowed to run build scripts (PNPM 10.1.0+). See the API page for the property: globalOnlyBuiltDependencies. The property is also added automatically by rush‑pnpm approve‑builds when you run it with PNPM 10.x. 🎉 However, the JSON schema used for validation – pnpm-config.schema.json – doesn’t yet list this field, so VS Code (which validates against the schema at https://developer.microsoft.com/json-schemas/rush/v5/pnpm-config.schema.json) flags it as “not allowed”. This is a schema‑documentation mismatch, not a Rush runtime error.  You can safely keep the property in your pnpm-config.json; it works as intended. If the warning is annoying, you can either:  * ignore it (the property is still processed by Rush),  * add a temporary entry for globalOnlyBuiltDependencies to a local copy of the schema, or  * wait for a schema update in a future Rush release that includes the new field.  The issue is with the schema, not with Rush itself. If you’d like to help, you could file a PR to update the schema to include globalOnlyBuiltDependencies.  Hope that clears things up! 🚀

[kgetz-arista]

@tluma Where does the schema file live? Is it in this repo somewhere?