-
Notifications
You must be signed in to change notification settings - Fork 105
Expand file tree
/
Copy pathpnpm-workspace.yaml
More file actions
104 lines (98 loc) · 3.22 KB
/
Copy pathpnpm-workspace.yaml
File metadata and controls
104 lines (98 loc) · 3.22 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
forceLegacyDeploy: true
packages:
- packages/*
- packages/grammarTools/*
- packages/memory/*
- packages/agents/*
- packages/agents/agentUtils/*
- packages/agents/*/host/webview
- packages/agentServer/*
- packages/dispatcher/*
- packages/utils/*
- packages/mcp/*
- packages/security/*
- examples/*
- examples/agentExamples/*
- examples/workflow/*
- extensions/*
- tools
- tools/*
# Require dependency versions to have been published at least 7 days
# (10080 minutes) ago before pnpm will resolve them. This keeps freshly
# published versions out of the lockfile until they have propagated to
# downstream mirrors/feeds and satisfied the organization's minimum
# package-age window, and it reduces exposure to compromised just-published
# releases. The constraint is applied at resolution time to all direct and
# transitive dependencies; installs from an existing frozen lockfile are not
# re-resolved and are therefore unaffected.
minimumReleaseAge: 10080
# In pnpm v11 the `onlyBuiltDependencies` / `ignoredBuiltDependencies` settings were
# replaced by `allowBuilds` (a map of package name -> true/false). Only the packages
# listed here are allowed to run install/build (postinstall) scripts.
# node-pty and protobufjs are intentionally set to false in pnpm v11, which
# disables their install scripts even though pnpm v10 allowed them. We keep
# them disabled to minimize install-time script execution in CI and local
# bootstrap unless explicitly re-enabled.
allowBuilds:
"@azure/msal-node-extensions": true
"@azure/msal-node-runtime": true
"@vscode/vsce-sign": true
better-sqlite3: true
canvas: true
electron: true
electron-winstaller: true
esbuild: true
exifreader: true
keytar: true
koffi: true
node-pty: false
onnxruntime-node: true
protobufjs: false
puppeteer: false
sharp: true
# Moved out of the deprecated `pnpm` field in package.json (pnpm v11 no longer reads it).
peerDependencyRules:
allowedVersions:
"@azure/core-rest-pipeline": "*"
jest: "*"
zod: "*"
ignoreMissing:
- eslint
- zod
allowedDeprecatedVersions:
"@cliqz/adblocker": "*"
"@cliqz/adblocker-content": "*"
"@cliqz/adblocker-extended-selectors": "*"
"@cliqz/adblocker-puppeteer": "*"
"@xmldom/xmldom": "<0.9.9"
abab: "*"
boolean: "*"
crx: "5"
domexception: "*"
glob: "<12"
inflight: "*"
lodash.isequal: "*"
node-domexception: "*"
prebuild-install: "*"
rimraf: "<4"
whatwg-encoding: "*"
supportedArchitectures:
cpu:
- x64
- arm64
overrides:
"@azure/core-xml": ">=1.5.0 <2.0.0"
"express>path-to-regexp": "0.1.13"
fast-xml-parser: ">=5.5.7 <6.0.0"
hono: ">=4.12.8 <5.0.0"
http-proxy-agent: ">=7.0.0 <8.0.0"
# Pin the Model Context Protocol SDK to 1.26.0. 1.29.0 added explicit `types`
# conditions to its `exports` that resolve the `./client/*.js` deep-import
# style (used across this repo) to a non-existent `*.js.d.ts`, breaking `tsc`
# under Node16 resolution; the no-extension alternative then breaks ESM
# runtime. Every package already declares `^1.26.0`; this only prevents drift.
"@modelcontextprotocol/sdk": "1.26.0"
node-forge: ">=1.4.0 <2.0.0"
node-gyp: "^12.2.0"
"router>path-to-regexp": ">=8.4.0 <9.0.0"
serialize-javascript: ">=7.0.5 <8.0.0"