Skip to content

The open alternative to Salesforce, designed for AI.

chore(security): bump undici to fixed versions everywhere (#27165)

Abdullah.f2054b4acefc
diff --git a/package.json b/package.json
index c4cbb13a88a..7c8337c0cb7 100644
--- a/package.json
+++ b/package.json
@@ -27,7 +27,7 @@
"name": "twenty-monorepo",
"packageManager": "[email protected]",
"resolutions": {
- "@module-federation/dts-plugin/undici": "^7.29.0",
+ "@module-federation/dts-plugin/undici": "^7.29.1",
"zapier-platform-core/form-data": "4.0.6",
"@remote-dom/react/@types/react": "^19.2.0",
"graphql": "16.8.1",
@@ -61,7 +61,7 @@
"@mintlify/models/axios": "1.20.0",
"nx/brace-expansion": "5.0.12"
},
- "//resolutions": "Each entry is load-bearing: it forces a version OUTSIDE some parent's declared range where no fixed upstream release exists; remove each once its blocker ships. @module-federation/dts-plugin/undici ^7.29.0 -> five undici advisories with in-major fixes (6.28.0 / 7.29.0 / 8.9.0): CVE-2026-13697 / GHSA-4cwx-7wf7-3272 (critical, cross-user information disclosure + parse-time crash via degenerate private cache directives) and CVE-2026-14643 / GHSA-jr45-8vmc-qm54, both >=7.0.0 <7.29.0 and >=8.0.0 <8.9.0, plus CVE-2026-15157 / GHSA-m8rv-5g2x-5cg5, CVE-2026-16728 / GHSA-8xcm-r25x-g524 and CVE-2026-16729 / GHSA-v3r7-h72x-cjcm (those three also <6.28.0). ^7.29.0 also still covers the six 7.28.0-fixed advisories the previous dts-plugin/undici ^7.28.0 entry was added for (GHSA-pr7r-676h-xcf6, GHSA-35p6-xmwp-9g52, GHSA-p88m-4jfj-68fv, GHSA-g8m3-5g58-fq7m, GHSA-hm92-r4w5-c3mj, GHSA-vmh5-mc38-953g). @module-federation/dts-plugin 2.5.1 pins undici 7.24.7 exact (latest 2.8.1 pins 7.28.0 exact, still vulnerable; transitive via @module-federation/cli + enhanced), so no parent upgrade carries the fix; scoped ^7.29.0 to stay inside major 7 -- no v8 API jump -- and every other consumer resolves a fixed version naturally within its own declared range: miniflare (exact-pinned by wrangler) pins 7.29.0 since the wrangler ^4.0.0 lift to 4.125.0, which retired the former miniflare/undici sibling entry; e2b's undici ^7.29.0 -> 7.29.0, node-gyp 12.4.0's ^6.25.0 -> 6.28.0, node-gyp 13's ^8.4.1 and jsdom 30's ^8.9.0 -> 8.9.0. Drop once dts-plugin depends on undici >=7.29.0. e2b's OPTIONAL ALIAS dependency undici8 (npm:undici@<exact>) needed its own alias-form entry while e2b 2.37.0 aliased it to 8.8.0, inside the >=8.0.0 <8.9.0 range above; the @e2b/code-interpreter ^2.6.0 lift to 2.7.1 brings e2b 2.45.0, whose alias is [email protected], so that entry was dropped. sharp@npm:0.33.5 + sharp@npm:^0.33.1 -> 0.35.4 are the only sharp entries left for GHSA-f88m-g3jw-g9cj (sharp inherits four libvips CVEs: CVE-2026-33327/33328/35590/35591, vulnerable <0.35.0, fixed 0.35.0) nor for GHSA-rgj7-g3m4-5g8c (sharp <0.35.4 bundles libheif with GHSA-g89c-p67h-r497 / GHSA-2jg2-4ch7-h545, fixed 0.35.4): the former next/sharp ^0.35.3 entry (next's copy ships in scanned images) was dropped once twenty-website's next ^16.2.6 lifted to 16.3.x, which pins sharp ^0.35.3 itself, with @react-email/ui's next forced onto that same version below -- twenty-sdk's direct sharp is bumped to ^0.35.3 in its own package.json, every caret consumer resolves 0.35.4 within its own range, and miniflare's exact pin reached 0.35.4 through the wrangler ^4.0.0 lift to 4.131.x (a [email protected] resolution was briefly considered for it and rejected in favour of that parent bump); @argos-ci/storybook 6.2.3 (twenty-front + twenty-ui) includes the iframe-restoration fix and uses @argos-ci/core 6.7.2 with sharp ^0.35.3, so no argos sharp resolution is needed. The former 6.0.x pin avoided unhandled Monaco worker errors, but retained an iframe-sizing bug that produced oversized screenshots; Monaco workers are now initialized in twenty-front's Storybook preview. sharp 0.33.5 (favicons 7.2.0 + @mintlify/prebuild, website/docs build tooling) sits in both advisory ranges; both parents are at their latest (@mintlify/prebuild 1.0.1255 still exact-pins favicons 7.2.0 and sharp 0.33.5) so no parent lift exists, and it is the last copy keeping Dependabot's root-lockfile sharp alert (#2077) open, so the two descriptors are forced to 0.35.4 -- the exact 0.33.5 pin and favicons' ^0.33.1 range, nothing else. Safe because favicons 7.3.1 itself moved to sharp ^0.35.3 with no API change on the calls favicons 7.2.0 makes; docs/website build only, never in the runtime images. Drop once @mintlify/prebuild pins sharp >=0.35.4 and a favicons that does the same. zapier-platform-core/form-data 4.0.6 -> CVE-2026-12143 / GHSA-hmw2-7cc7-3qxx (form-data CRLF injection via unescaped multipart field names and filenames, vulnerable >=4.0.0 <4.0.6); zapier-platform-core 19.0.0 hard-pins form-data 4.0.5 exact (no caret, still 4.0.5 in its latest) so no parent upgrade carries the fix; scoped to it as the sole 4.0.5 pinner -- every other form-data consumer resolves 4.0.6 naturally via its ^4.0.x range, so the pin dedupes onto it (nx was the other pinner until 22.7.7 moved it to 4.0.6, so its entry was dropped); drop once zapier-platform-core depends on form-data >=4.0.6. (nodemailer needs NO entry: twenty-server and the seed-dependencies declare ^10.0.12 directly, which covers the September-2026 nodemailer advisories fixed across 10.0.2-10.0.9 (GHSA-6vj9-mwq6-2f5v, GHSA-8vvx-rff5-p5rq, GHSA-v53p-9fqp-m79j, GHSA-prgh-xp8r-p3m5, GHSA-g57g-f23g-4646) as well as the earlier 9.1.x ones; v10 ships its own TypeScript declarations, so @types/nodemailer was removed, and imapflow -- which exact-pinned nodemailer through its whole 1.x line -- was lifted to 2.0.2, which drops the nodemailer dependency.) @mintlify/scraping/puppeteer 25.10.0 -> two HIGH extract-zip advisories with NO patched release (extract-zip 2.0.1 is the last release, 2020): GHSA-jmr9-qjv8-65gv (unvalidated symlink path traversal) and GHSA-7pqw-9j4j-h8q3 / CVE-2026-19693. The only consumer is @puppeteer/browsers, which dropped extract-zip for modern-tar in its 3.x line; puppeteer >=25 carries @puppeteer/browsers 3.x, but @mintlify/scraping exact-pins puppeteer 24.3.1 and still does in its latest 4.0.1013, so no parent lift exists. Scoped to @mintlify/scraping (docs tooling, the sole puppeteer consumer in the tree); held at 25.10.0 because 25.11.0 (2026-09-14) is inside the 3d npmMinimalAgeGate. With this pin extract-zip leaves the lockfile entirely. Drop once @mintlify/scraping pins puppeteer >=25. nx/brace-expansion 5.0.12 -> the September-2026 brace-expansion advisories: GHSA-q2hr-2g5m-vwhr (MEDIUM, quadratic-time expansion of the `{a},b}` rewrite), GHSA-6j4f-fj2g-mc7p and GHSA-qhr7-859c-m2p7 (both HIGH, DoS via uncontrolled recursion), all fixed in 5.0.12 on the 5.x line (1.1.21 / 2.1.7 on the older lines). nx exact-pins brace-expansion 5.0.8 and its latest releases still pin vulnerable versions (22.7.12 pins 5.0.8, 23.2.1 pins 5.0.9), so no parent upgrade carries the fix; scoped to nx (its sole exact pinner) -- every other consumer's caret range (^1.1.7 via minimatch 3, ^2.0.x, ^5.0.x) resolves a fixed version on its own; drop once nx pins >=5.0.12. nx/smol-toml 1.7.1 -> GHSA-7w5x-hrqm-74c2 / CVE-2026-85730 (HIGH, DoS via malformed TOML documents, vulnerable <=1.7.0, fixed 1.7.1); nx exact-pins smol-toml 1.6.1 and still does in its latest 23.2.1, so no parent upgrade carries the fix; scoped to nx (its sole consumer); drop once nx pins >=1.7.1. (the former @nestjs/graphql/ws 8.21.0 pin for CVE-2026-48779 was dropped once @nestjs/graphql moved 13.4.2 -> 13.4.5, which pins ws 8.21.3 itself; twenty-server's resolver-scoping patch was rebased onto 13.4.5 for that lift.) @remote-dom/react/@types/react ^19.2.0 -> React type-identity dedup, SCOPED to @remote-dom/react only (every other package resolves @types/react 19 naturally from the workspace ^19.2.0 ranges). @remote-dom/react (transitive via twenty-front-component-renderer) lists @types/react ^18 in its own dependencies and nests its own copy; React 18 and 19 declare ReactNode differently (19 adds bigint + Promise<AwaitedReactNode>, drops ReactFragment's {}), so the two copies are mutually non-assignable and break twenty-front's typecheck (~156 TS2322 errors). Range-aligning our own packages can't fix a third-party's transitive @types pin, hence this single scoped override (only @types/react splits; runtime react/react-dom are peer-deps that converge naturally, and @types/react-dom does not nest a copy). Drop once @remote-dom/react widens @types/react to ^19 (latest 1.2.2 still pins ^18; tracked upstream in Shopify/remote-dom#153). graphql 16.8.1 -> singleton pin held below msw's ^16.12.0 dep and @nestjs/graphql's ^16.11.0 peer; drop after a validated repo-wide bump to latest 16.x; graphql-redis-subscriptions/ioredis 5.10.1 -> TS type-identity dedup: twenty-server passes its ioredis client into RedisPubSub, so this must equal the exact ioredis version pinned by twenty-server and bullmq (bump in lockstep); @types/qs 6.9.16 -> holdback below the 6.9.17 ParsedQs typing break (node-saml wants ^6.9.18); @opentelemetry/api 1.9.1 -> singleton guard for the NoopMeterProvider bug (#20231): ai 6.0.x pins 1.9.0 exact vs @sentry/node ^1.9.1, drop when workspace ai >=6.0.178 AND @scalar/agent-chat moves off ai 6.0.33; chokidar ^3 -> NestJS CLI watch needs fsevents on macOS, removed in chokidar 4/5 (#20316); tmp ^0.2.7 -> CVE, zapier-platform-cli 19 (latest) pins 0.2.5 and inquirer 7/8's external-editor wants ^0.0.33; (the former @mintlify/previewing/tar pin was dropped once the mintlify 4.2.816 lift brought a previewing that pins tar 7.5.21 itself.) @angular-devkit/core 19.2.24 -> picomatch CVE, blocked on @nestjs/cli >11.0.23 fixing the dist/src output regression (repo held at 11.0.16); yeoman-environment 6.0.1 -> CVE, zapier-platform-cli 19 (latest) pins 4.4.3; express/qs 6.16.0 -> two MEDIUM qs advisories fixed in 6.16.0: GHSA-4mjr-xmp4-gh2g / CVE-2026-82417 (DoS via attacker-controlled isBuffer, >=2.2.5 <6.16.0) and GHSA-x5fp-wj9c-mxmx / CVE-2026-82562 (array-limit bypass via bracket-key comma parsing, >=6.14.2 <=6.15.3; lifted from the 6.15.2 pin that covered CVE-2026-8723 / GHSA-q8mj-m7cp-5q26) for old express 4.22.x exact-pinned by @mintlify/previewing (4.22.0 / 4.22.2; its latest 4.0.1371 still pins 4.22.0, while express 4.22.3 itself moved to qs ~6.16.0, so the parent is the blocker); body-parser needs NO entry: the ~1.20.x consumers were lifted in-range to 1.20.8, whose qs ~6.16.0 reaches the fix on its own, and the caret-range qs consumers dedupe onto 6.16.0 naturally; drop once @mintlify/previewing moves off express 4.x or pins >=4.22.3; No postcss resolution remains for the postcss CVEs, latest GHSA-r28c-9q8g-f849 (path traversal in previous source map auto-loading via sourceMappingURL, arbitrary .map file disclosure, vulnerable <=8.5.17, fixed 8.5.18): next 16.3.2 pins 8.5.23 exact itself (the former next/postcss 8.5.23 entry went with the same next lift), the caret consumers (^8.4.38, ^8.4.47, ^8.5.15) dedupe onto 8.5.23 naturally, and @mintlify/common's entry was dropped once the mintlify 4.2.816 lift brought a common that pins 8.5.23 itself; No uuid resolution remains: googleapis-common 8.0.1 (forced via googleapis/googleapis-common) has no uuid dependency so googleapis-common/uuid was dropped, sockjs's entry went when sockjs left the tree and @cypress/request's when the verdaccio lift brought 4.0.1 which has no uuid dependency. @cyntler/react-doc-viewer/ajv 8.20.0 -> CVE, upstream (latest 1.17.1) pins ajv ^7 but never imports it, forcing v8 is safe; */esbuild 0.28.1 -> two esbuild advisories both fixed in 0.28.1: the Deno-module binary-integrity RCE GHSA-gv7w-rqvm-qjhr (vulnerable >=0.17.0 <0.28.1) and the earlier dev-server path-traversal GHSA-g7r4-m6w7-qqqr (Windows, >=0.27.3 <0.28.1). The Deno advisory's range covers every esbuild <0.28.1, so it re-exposed older transitive copies too. Preference is to fix by upgrading the parent, not by resolution -- done where it works: @size-limit/preset-small-lib+size-limit (now ^12.1.0, pin esbuild ^0.28.0) and wrangler (bumped within ^4.0.0 to 4.102.0, which pins esbuild 0.28.1) were bumped and resolve to 0.28.1 on their own, NO resolution needed. The three resolutions below are for parents that pin a vulnerable esbuild OUTSIDE the 0.28.1 range in their latest release: @opennextjs/aws exact-pins 0.25.4 (still 0.25.4 in latest 4.1.0); zapier-platform-cli exact-pins 0.25.8 (still 0.25.8 in latest 19.1.0); @lingui/cli 5.x pins ^0.25.1 -> caps <0.26 (6.x drops esbuild entirely but is a major migration). @react-email/ui (6.9.0 exact-pins 0.28.1), react-email (^0.28.0, no longer down-selected now that 0.28.1 has aged past the npmMinimalAgeGate) and storybook (10.4.6 widened its range to include ^0.28.0) resolve >=0.28.1 on their own, so their entries were dropped. tsx needs NO resolution: its ^4.x ranges resolve to 4.22.x which pins esbuild ~0.28.0 -> 0.28.1 on its own. (tsx had briefly been pinned to 4.21.0 because tsx 4.22's --import tsx/esm loader feeds esbuild-downleveled enums into jest's type-checking ts-node config compiler, yielding a spurious TS7022 in server-integration-test; that is now fixed at the source by dropping --import tsx/esm from the integration jest invocation in twenty-server project.json (it had been swept in by the Storybook 10 upgrade and is not needed there): ts-node alone now compiles the config + globalSetup, so there is no esbuild enum downleveling to trip TS7022 and decorator metadata is still emitted. tsx version is now irrelevant to the tests, so the pin was dropped.) Drop each entry once its parent ships a range that resolves to >=0.28.1 on its own. Our own twenty-client-sdk raises its esbuild floor to ^0.28.1 directly in its package.json instead of via a resolution. googleapis/googleapis-common 8.0.1 -> singleton dedup for the googleapis 173 upgrade. googleapis-common 8.0.2 (published 2026-06-04, AFTER googleapis 173 on 2026-05-28) regressed its google-auth-library dep from a range to exact 10.5.0 (and gaxios to exact 7.1.3), while googleapis itself pulls google-auth-library ^10.2.0 (10.7.0); the two mismatched copies make OAuth2Client's type-identity diverge between the client our provider builds (via googleapis -> 10.7.0) and the one gmail/calendar method options expect (via googleapis-common -> 10.5.0), breaking every gmail/calendar service typecheck (TS2322/TS2769). The parents are already at latest (googleapis 173.0.0, googleapis-common 8.0.2) so we cannot fix by upgrading; instead we pin googleapis' googleapis-common back to 8.0.1, the last version with RANGE deps (google-auth-library ^10.1.0, gaxios ^7.0.0-rc.4) -- and the version googleapis 173 originally shipped against. Ranges resolve to the same hoisted versions googleapis uses, so google-auth-library AND gaxios both collapse to a single copy with no further resolution (a global google-auth-library pin would only dedup one of the two). Scoped to googleapis since it is the sole googleapis-common 8.x consumer. Drop once googleapis-common 8.0.3+ restores range deps or googleapis bumps to a common that does. js-yaml@npm:4.3.1 -> 4.3.2 -> GHSA-2883-xcg3-v3hh / CVE-2026-84375 (HIGH, maxTotalMergeKeys does not limit CPU use for empty merge sources, vulnerable >=4.0.0 <4.3.2, fixed 4.3.2; the 3.x line has its own 3.15.2 backport, which @istanbuljs/load-nyc-config's ^3.13.1 reaches on its own). The six @mintlify/* packages (cli, common, prebuild, previewing, scraping, validation) exact-pin js-yaml 4.3.1 and still do in the latest mintlify 4.2.892 / @mintlify/cli 4.0.1495, so no parent upgrade carries the fix; a single descriptor-keyed entry replaces six parent-scoped ones and touches only that exact 4.3.1 pin (every caret consumer dedupes onto 4.3.2 naturally). Their previous six pins had been dropped once the mintlify 4.2.816 lift brought a chain pinning 4.3.1 itself; drop once mintlify pins >=4.3.2. Of the two js-yaml 3.x consumers (both declaring ^3.13.1): @istanbuljs/[email protected] (via babel-plugin-istanbul coverage) is UNPINNED -- the 3.x line shipped backports for every js-yaml advisory (3.15.0 fixes GHSA-h67p-54hq-rp68 + GHSA-52cp-r559-cp3m, 3.15.1 fixes GHSA-5p4m-2wfm-xmqj), so it resolves a clean 3.15.1 within its own range, and as build-only coverage tooling that is enough. [email protected] (via mintlify in twenty-docs) stays FORCED to 4.3.2 (front-matter/js-yaml, lifted in step with the entry above) as a deliberate posture call: 4.x is the maintained js-yaml line, while the 3.x fixes were backports to a legacy major that future advisories may not get, and front-matter parses docs content. Because js-yaml 4.x removed the safeLoad API front-matter's default path calls, the companion patch (front-matter@npm:4.0.2 -> .yarn/patches/front-matter-npm-4.0.2-e1cc0efa69.patch) sets loader = parser.load (safe-by-default in 4.x); pin and patch are a matched pair -- the patch without the pin would select 3.x's UNSAFE full-schema load, so they must only ever be dropped together. The version move stays a separate resolution because a yarn patch only rewrites a package's files, not its resolved dependency graph. Drop both once mintlify moves front-matter off js-yaml 3.x or drops it. @react-email/ui/next 16.3.5 -> Next.js July-2026 security release (CVE-2026-64641 App-Router Server-Actions DoS, CVE-2026-64645 rewrites/redirects SSRF + open redirect, and the sibling CVE-2026-64642..64648), vulnerable >=16.0.0 <16.2.11, fixed 16.2.11; @react-email/ui 6.9.0 hard-pins next 16.2.6 exact (transitive via react-email in twenty-emails). The parent bump was ATTEMPTED and reverted: @react-email/ui + react-email ^6.9.2 do carry next 16.3.0, but that pulls a SECOND next (16.3.0 alongside twenty-website's 16.3.2) plus its dependency subtree into the lockfile -- the scoped pin here forces @react-email/ui's next to the version twenty-website already resolves within ^16.2.6 (16.3.5 since the September-2026 CRITICAL unauthenticated-RCE advisories GHSA-p293-qw3h-jr36 / CVE-2026-75604 on Windows-hosted servers and GHSA-2xp9-vwfh-vxw4 in the Image Optimization API with AVIF input, both >=16.0.0 <16.3.3, fixed 16.3.3), so it dedupes with ZERO new packages, which is the leaner outcome for a security PR. So @react-email/ui is held at ^6.9.0 with this scoped pin; drop once @react-email/ui itself depends on the next version twenty-website resolves. mintlify axios + adm-zip (twenty-docs) -> bumped mintlify ^4.2.594 -> ^4.2.790 (resolves 4.2.816), which pulls @mintlify/cli >=4.0.1393 -> adm-zip 0.6.0 (fixes CVE-2026-39244 / GHSA-xcpc-8h2w-3j85 for the @mintlify/cli + @mintlify/previewing copies) AND @mintlify/models >=0.0.347 -> axios 1.18.0 (fixes CVE-2026-44494 / SNYK-JS-AXIOS-17111079 axios prototype pollution via config.proxy, vulnerable >=1.15.2 <1.18.0). This one parent bump REPLACED three former scoped resolutions (@mintlify/models/axios, @mintlify/cli/adm-zip, @mintlify/previewing/adm-zip). Blast radius was measured and is contained: ~56 lockfile descriptors change, ALL inside twenty-docs' mintlify subtree (shiki/twoslash, remark/mdx, puppeteer 22->24, and a NESTED type-fest v5) -- the root-hoisted type-fest stays v4 (4.41.0) and every twenty-* workspace package declares type-fest 4.x, so type-fest v5 lives only inside mintlify's own nested tree and touches no workspace typecheck. All typechecks pass (twenty-front / -website / -emails / -ui / -shared reliably; twenty-server passes too modulo the pre-existing flaky tsgo 7.0.0-dev stack-overflow that hits ~1 run in 5 with ZERO type errors), and the mintlify CLI's harmless nested-React 'invalid hook call' warning is byte-identical before and after the bump. nx/axios 1.20.0 + @mintlify/models/axios 1.20.0 -> the September-2026 axios advisory batch, twelve advisories all fixed in 1.20.0, including the HIGH prototype-pollution gadgets GHSA-x97p-jq2g-jp4f / GHSA-m8m8-qj5v-23w3, the HTTP/2 DNS/proxy-control bypass GHSA-3pq3-5fj3-cg6v, the fetch-adapter maxRedirects bypass GHSA-r4gj-5m52-g5wh, the HTTP/2 unhandled-error DoS GHSA-542g-h47m-68v8 and the two ReDoS advisories GHSA-c29m-xwm3-cm6r / GHSA-mghh-pgcx-3jjj (vulnerable ranges vary per advisory, all <1.20.0). Every caret consumer (twenty-server + twenty-sdk ^1.16.0, and transitives) resolves 1.20.0 on its own; these two parents exact-pin a vulnerable axios in their LATEST releases, so no parent upgrade carries the fix: nx pins 1.18.1 through 22.7.12 and 23.2.1 alike, and @mintlify/models pins 1.18.0 through its latest 0.0.363 (mintlify 4.2.964). Both entries are RE-ADDITIONS of previously dropped pins (see below) now that the parents have fallen behind again; drop each once its parent ships axios >=1.20.0. (The former nx/axios pin had been dropped when nx 22.7.7+ moved to axios 1.18.1, >=1.18.0 -- sufficient for the old config.proxy advisory, not for this batch.) adm-zip -> 0.6.1 for the September-2026 adm-zip advisory batch, all vulnerable <=0.6.0 and fixed in 0.6.1: GHSA-8238-w5pm-2374 (HIGH, unhandled error event in async DEFLATE decompression crashes the process), GHSA-rcw4-f5rp-g42v (HIGH, the decompression-bomb guard added for CVE-2026-39244 can be bypassed), GHSA-j5f4-cc29-5x44 (HIGH, extraction preserves SUID/SGID bits from untrusted archives), GHSA-c6fg-446q-cg94 (getDataAsync() bypasses the maxOutputLength guard) and GHSA-p634-w6r4-rjp2 (duplicate entry names resolve inconsistently between getEntry() and extractAllTo()); 0.6.1 also still covers CVE-2026-39244 / GHSA-xcpc-8h2w-3j85 (unbounded Buffer.alloc from a declared uncompressed size, fixed 0.6.0) that the earlier 0.6.0 pins were added for. All FOUR consumers exact-pin a vulnerable adm-zip in their latest releases, so each keeps its OWN scoped pin (not a global one) with its own drop condition: @mintlify/cli and @mintlify/previewing pin 0.6.0 (still 0.6.0 in @mintlify/cli 4.0.1573 / @mintlify/previewing 4.0.1428, mintlify 4.2.970) -- these two entries are RE-ADDITIONS, dropped when the mintlify 4.2.816 lift brought 0.6.0, sufficient then but not for this batch; zapier-platform-cli pins 0.5.16 (still 0.5.16 in its latest 19.1.0, cf. its sibling zapier-platform-core/form-data + zapier-platform-cli/esbuild pins); @module-federation/dts-plugin 2.5.1 pins 0.5.10 (dts-plugin 2.9.2 moves to ^0.6.1, but @nx/module-federation 22.7.8 holds the module-federation stack at ^2.3.3 -> 2.5.1, so reaching it means forcing the whole build-critical module-federation runtime up or bumping all of nx to 23.x -- disproportionate, and it sits alongside the existing @module-federation/dts-plugin/undici pin for the same package and reason). 0.6.0 -> 0.6.1 is a patch release; the 0.6.0 major's breaking changes (extractEntryTo preserving subdirectories, engines Node >=14) were already absorbed by the zapier and dts-plugin pins, and the mintlify copies were already on 0.6.0. Drop the two mintlify pins once @mintlify/cli and @mintlify/previewing ship adm-zip >=0.6.1; drop the zapier pin once zapier-platform-cli does; drop the dts-plugin pin once @nx/module-federation carries module-federation >=2.9.2.",
+ "//resolutions": "Each entry is load-bearing: it forces a version OUTSIDE some parent's declared range where no fixed upstream release exists; remove each once its blocker ships. @module-federation/dts-plugin/undici ^7.29.1 -> the September-2026 undici advisory batch, all fixed in 6.28.1 / 7.29.1 / 8.10.2: GHSA-rfgv-xxqx-mfg5 (HIGH, DoS via unrequested WebSocket subprotocol), GHSA-w293-vg96-wgc3 (HIGH, TLS certificate validation bypass via dropped connection), GHSA-vp8m-p9jh-q5pm (HIGH, cross-origin cache poisoning, 8.x only), GHSA-3wwx-pv8p-q78v, GHSA-2jfj-6hjv-fm6j, GHSA-3xpg-4rpp-hhhm, GHSA-pmjh-fq2x-6v4x, GHSA-rx4f-c7p8-82vq and the low-severity GHSA-r53p-7pc4-xj5r, GHSA-2gqq-gqf2-x968, GHSA-8436-99hf-9mmv; dts-plugin 2.5.1 still pins undici 7.24.7 exact (2.9.2 pins 7.29.1, but the module-federation stack is held at 2.5.1 by @nx/module-federation), so the floor moves from ^7.29.0 to ^7.29.1. miniflare (exact-pinned by wrangler) reaches 7.29.1 itself through the wrangler ^4.0.0 lift to 4.144.0, and every other consumer resolves a fixed version within its own range. The pin was originally ^7.29.0 for five earlier undici advisories with in-major fixes (6.28.0 / 7.29.0 / 8.9.0): CVE-2026-13697 / GHSA-4cwx-7wf7-3272 (critical, cross-user information disclosure + parse-time crash via degenerate private cache directives) and CVE-2026-14643 / GHSA-jr45-8vmc-qm54, both >=7.0.0 <7.29.0 and >=8.0.0 <8.9.0, plus CVE-2026-15157 / GHSA-m8rv-5g2x-5cg5, CVE-2026-16728 / GHSA-8xcm-r25x-g524 and CVE-2026-16729 / GHSA-v3r7-h72x-cjcm (those three also <6.28.0). ^7.29.0 also still covers the six 7.28.0-fixed advisories the previous dts-plugin/undici ^7.28.0 entry was added for (GHSA-pr7r-676h-xcf6, GHSA-35p6-xmwp-9g52, GHSA-p88m-4jfj-68fv, GHSA-g8m3-5g58-fq7m, GHSA-hm92-r4w5-c3mj, GHSA-vmh5-mc38-953g). @module-federation/dts-plugin 2.5.1 pins undici 7.24.7 exact (latest 2.8.1 pins 7.28.0 exact, still vulnerable; transitive via @module-federation/cli + enhanced), so no parent upgrade carries the fix; scoped ^7.29.0 to stay inside major 7 -- no v8 API jump -- and every other consumer resolves a fixed version naturally within its own declared range: miniflare (exact-pinned by wrangler) needed no sibling entry once the wrangler ^4.0.0 lift to 4.125.0 brought 7.29.0, and now 7.29.1 via 4.144.0; e2b's undici ^7.29.1 -> 7.30.0, node-gyp 12.4.0's ^6.25.0 -> 6.29.0, node-gyp 13's ^8.4.1 and jsdom 30's ^8.9.0 -> 8.11.2. Drop once dts-plugin depends on undici >=7.29.1. e2b's OPTIONAL ALIAS dependency undici8 (npm:undici@<exact>) is never touched by the scoped entry above and needs a fixed alias of its own: the @e2b/code-interpreter ^2.6.0 lift to 2.7.1 brought e2b 2.45.0 aliasing [email protected], which retired an earlier alias-form entry but is still inside the September-2026 batch's 8.x range (<8.10.2, incl. the 8.x-only GHSA-vp8m-p9jh-q5pm); e2b's ^2.39.0 range lifts in-range to 2.51.0, which aliases [email protected] (and raises its own undici floor to ^7.29.1), so no alias-form resolution is needed. sharp@npm:0.33.5 + sharp@npm:^0.33.1 -> 0.35.4 are the only sharp entries left for GHSA-f88m-g3jw-g9cj (sharp inherits four libvips CVEs: CVE-2026-33327/33328/35590/35591, vulnerable <0.35.0, fixed 0.35.0) nor for GHSA-rgj7-g3m4-5g8c (sharp <0.35.4 bundles libheif with GHSA-g89c-p67h-r497 / GHSA-2jg2-4ch7-h545, fixed 0.35.4): the former next/sharp ^0.35.3 entry (next's copy ships in scanned images) was dropped once twenty-website's next ^16.2.6 lifted to 16.3.x, which pins sharp ^0.35.3 itself, with @react-email/ui's next forced onto that same version below -- twenty-sdk's direct sharp is bumped to ^0.35.3 in its own package.json, every caret consumer resolves 0.35.4 within its own range, and miniflare's exact pin reached 0.35.4 through the wrangler ^4.0.0 lift to 4.131.x (a [email protected] resolution was briefly considered for it and rejected in favour of that parent bump); @argos-ci/storybook 6.2.3 (twenty-front + twenty-ui) includes the iframe-restoration fix and uses @argos-ci/core 6.7.2 with sharp ^0.35.3, so no argos sharp resolution is needed. The former 6.0.x pin avoided unhandled Monaco worker errors, but retained an iframe-sizing bug that produced oversized screenshots; Monaco workers are now initialized in twenty-front's Storybook preview. sharp 0.33.5 (favicons 7.2.0 + @mintlify/prebuild, website/docs build tooling) sits in both advisory ranges; both parents are at their latest (@mintlify/prebuild 1.0.1255 still exact-pins favicons 7.2.0 and sharp 0.33.5) so no parent lift exists, and it is the last copy keeping Dependabot's root-lockfile sharp alert (#2077) open, so the two descriptors are forced to 0.35.4 -- the exact 0.33.5 pin and favicons' ^0.33.1 range, nothing else. Safe because favicons 7.3.1 itself moved to sharp ^0.35.3 with no API change on the calls favicons 7.2.0 makes; docs/website build only, never in the runtime images. Drop once @mintlify/prebuild pins sharp >=0.35.4 and a favicons that does the same. zapier-platform-core/form-data 4.0.6 -> CVE-2026-12143 / GHSA-hmw2-7cc7-3qxx (form-data CRLF injection via unescaped multipart field names and filenames, vulnerable >=4.0.0 <4.0.6); zapier-platform-core 19.0.0 hard-pins form-data 4.0.5 exact (no caret, still 4.0.5 in its latest) so no parent upgrade carries the fix; scoped to it as the sole 4.0.5 pinner -- every other form-data consumer resolves 4.0.6 naturally via its ^4.0.x range, so the pin dedupes onto it (nx was the other pinner until 22.7.7 moved it to 4.0.6, so its entry was dropped); drop once zapier-platform-core depends on form-data >=4.0.6. (nodemailer needs NO entry: twenty-server and the seed-dependencies declare ^10.0.12 directly, which covers the September-2026 nodemailer advisories fixed across 10.0.2-10.0.9 (GHSA-6vj9-mwq6-2f5v, GHSA-8vvx-rff5-p5rq, GHSA-v53p-9fqp-m79j, GHSA-prgh-xp8r-p3m5, GHSA-g57g-f23g-4646) as well as the earlier 9.1.x ones; v10 ships its own TypeScript declarations, so @types/nodemailer was removed, and imapflow -- which exact-pinned nodemailer through its whole 1.x line -- was lifted to 2.0.2, which drops the nodemailer dependency.) @mintlify/scraping/puppeteer 25.10.0 -> two HIGH extract-zip advisories with NO patched release (extract-zip 2.0.1 is the last release, 2020): GHSA-jmr9-qjv8-65gv (unvalidated symlink path traversal) and GHSA-7pqw-9j4j-h8q3 / CVE-2026-19693. The only consumer is @puppeteer/browsers, which dropped extract-zip for modern-tar in its 3.x line; puppeteer >=25 carries @puppeteer/browsers 3.x, but @mintlify/scraping exact-pins puppeteer 24.3.1 and still does in its latest 4.0.1013, so no parent lift exists. Scoped to @mintlify/scraping (docs tooling, the sole puppeteer consumer in the tree); held at 25.10.0 because 25.11.0 (2026-09-14) is inside the 3d npmMinimalAgeGate. With this pin extract-zip leaves the lockfile entirely. Drop once @mintlify/scraping pins puppeteer >=25. nx/brace-expansion 5.0.12 -> the September-2026 brace-expansion advisories: GHSA-q2hr-2g5m-vwhr (MEDIUM, quadratic-time expansion of the `{a},b}` rewrite), GHSA-6j4f-fj2g-mc7p and GHSA-qhr7-859c-m2p7 (both HIGH, DoS via uncontrolled recursion), all fixed in 5.0.12 on the 5.x line (1.1.21 / 2.1.7 on the older lines). nx exact-pins brace-expansion 5.0.8 and its latest releases still pin vulnerable versions (22.7.12 pins 5.0.8, 23.2.1 pins 5.0.9), so no parent upgrade carries the fix; scoped to nx (its sole exact pinner) -- every other consumer's caret range (^1.1.7 via minimatch 3, ^2.0.x, ^5.0.x) resolves a fixed version on its own; drop once nx pins >=5.0.12. nx/smol-toml 1.7.1 -> GHSA-7w5x-hrqm-74c2 / CVE-2026-85730 (HIGH, DoS via malformed TOML documents, vulnerable <=1.7.0, fixed 1.7.1); nx exact-pins smol-toml 1.6.1 and still does in its latest 23.2.1, so no parent upgrade carries the fix; scoped to nx (its sole consumer); drop once nx pins >=1.7.1. (the former @nestjs/graphql/ws 8.21.0 pin for CVE-2026-48779 was dropped once @nestjs/graphql moved 13.4.2 -> 13.4.5, which pins ws 8.21.3 itself; twenty-server's resolver-scoping patch was rebased onto 13.4.5 for that lift.) @remote-dom/react/@types/react ^19.2.0 -> React type-identity dedup, SCOPED to @remote-dom/react only (every other package resolves @types/react 19 naturally from the workspace ^19.2.0 ranges). @remote-dom/react (transitive via twenty-front-component-renderer) lists @types/react ^18 in its own dependencies and nests its own copy; React 18 and 19 declare ReactNode differently (19 adds bigint + Promise<AwaitedReactNode>, drops ReactFragment's {}), so the two copies are mutually non-assignable and break twenty-front's typecheck (~156 TS2322 errors). Range-aligning our own packages can't fix a third-party's transitive @types pin, hence this single scoped override (only @types/react splits; runtime react/react-dom are peer-deps that converge naturally, and @types/react-dom does not nest a copy). Drop once @remote-dom/react widens @types/react to ^19 (latest 1.2.2 still pins ^18; tracked upstream in Shopify/remote-dom#153). graphql 16.8.1 -> singleton pin held below msw's ^16.12.0 dep and @nestjs/graphql's ^16.11.0 peer; drop after a validated repo-wide bump to latest 16.x; graphql-redis-subscriptions/ioredis 5.10.1 -> TS type-identity dedup: twenty-server passes its ioredis client into RedisPubSub, so this must equal the exact ioredis version pinned by twenty-server and bullmq (bump in lockstep); @types/qs 6.9.16 -> holdback below the 6.9.17 ParsedQs typing break (node-saml wants ^6.9.18); @opentelemetry/api 1.9.1 -> singleton guard for the NoopMeterProvider bug (#20231): ai 6.0.x pins 1.9.0 exact vs @sentry/node ^1.9.1, drop when workspace ai >=6.0.178 AND @scalar/agent-chat moves off ai 6.0.33; chokidar ^3 -> NestJS CLI watch needs fsevents on macOS, removed in chokidar 4/5 (#20316); tmp ^0.2.7 -> CVE, zapier-platform-cli 19 (latest) pins 0.2.5 and inquirer 7/8's external-editor wants ^0.0.33; (the former @mintlify/previewing/tar pin was dropped once the mintlify 4.2.816 lift brought a previewing that pins tar 7.5.21 itself.) @angular-devkit/core 19.2.24 -> picomatch CVE, blocked on @nestjs/cli >11.0.23 fixing the dist/src output regression (repo held at 11.0.16); yeoman-environment 6.0.1 -> CVE, zapier-platform-cli 19 (latest) pins 4.4.3; express/qs 6.16.0 -> two MEDIUM qs advisories fixed in 6.16.0: GHSA-4mjr-xmp4-gh2g / CVE-2026-82417 (DoS via attacker-controlled isBuffer, >=2.2.5 <6.16.0) and GHSA-x5fp-wj9c-mxmx / CVE-2026-82562 (array-limit bypass via bracket-key comma parsing, >=6.14.2 <=6.15.3; lifted from the 6.15.2 pin that covered CVE-2026-8723 / GHSA-q8mj-m7cp-5q26) for old express 4.22.x exact-pinned by @mintlify/previewing (4.22.0 / 4.22.2; its latest 4.0.1371 still pins 4.22.0, while express 4.22.3 itself moved to qs ~6.16.0, so the parent is the blocker); body-parser needs NO entry: the ~1.20.x consumers were lifted in-range to 1.20.8, whose qs ~6.16.0 reaches the fix on its own, and the caret-range qs consumers dedupe onto 6.16.0 naturally; drop once @mintlify/previewing moves off express 4.x or pins >=4.22.3; No postcss resolution remains for the postcss CVEs, latest GHSA-r28c-9q8g-f849 (path traversal in previous source map auto-loading via sourceMappingURL, arbitrary .map file disclosure, vulnerable <=8.5.17, fixed 8.5.18): next 16.3.2 pins 8.5.23 exact itself (the former next/postcss 8.5.23 entry went with the same next lift), the caret consumers (^8.4.38, ^8.4.47, ^8.5.15) dedupe onto 8.5.23 naturally, and @mintlify/common's entry was dropped once the mintlify 4.2.816 lift brought a common that pins 8.5.23 itself; No uuid resolution remains: googleapis-common 8.0.1 (forced via googleapis/googleapis-common) has no uuid dependency so googleapis-common/uuid was dropped, sockjs's entry went when sockjs left the tree and @cypress/request's when the verdaccio lift brought 4.0.1 which has no uuid dependency. @cyntler/react-doc-viewer/ajv 8.20.0 -> CVE, upstream (latest 1.17.1) pins ajv ^7 but never imports it, forcing v8 is safe; */esbuild 0.28.1 -> two esbuild advisories both fixed in 0.28.1: the Deno-module binary-integrity RCE GHSA-gv7w-rqvm-qjhr (vulnerable >=0.17.0 <0.28.1) and the earlier dev-server path-traversal GHSA-g7r4-m6w7-qqqr (Windows, >=0.27.3 <0.28.1). The Deno advisory's range covers every esbuild <0.28.1, so it re-exposed older transitive copies too. Preference is to fix by upgrading the parent, not by resolution -- done where it works: @size-limit/preset-small-lib+size-limit (now ^12.1.0, pin esbuild ^0.28.0) and wrangler (bumped within ^4.0.0 to 4.102.0, which pins esbuild 0.28.1) were bumped and resolve to 0.28.1 on their own, NO resolution needed. The three resolutions below are for parents that pin a vulnerable esbuild OUTSIDE the 0.28.1 range in their latest release: @opennextjs/aws exact-pins 0.25.4 (still 0.25.4 in latest 4.1.0); zapier-platform-cli exact-pins 0.25.8 (still 0.25.8 in latest 19.1.0); @lingui/cli 5.x pins ^0.25.1 -> caps <0.26 (6.x drops esbuild entirely but is a major migration). @react-email/ui (6.9.0 exact-pins 0.28.1), react-email (^0.28.0, no longer down-selected now that 0.28.1 has aged past the npmMinimalAgeGate) and storybook (10.4.6 widened its range to include ^0.28.0) resolve >=0.28.1 on their own, so their entries were dropped. tsx needs NO resolution: its ^4.x ranges resolve to 4.22.x which pins esbuild ~0.28.0 -> 0.28.1 on its own. (tsx had briefly been pinned to 4.21.0 because tsx 4.22's --import tsx/esm loader feeds esbuild-downleveled enums into jest's type-checking ts-node config compiler, yielding a spurious TS7022 in server-integration-test; that is now fixed at the source by dropping --import tsx/esm from the integration jest invocation in twenty-server project.json (it had been swept in by the Storybook 10 upgrade and is not needed there): ts-node alone now compiles the config + globalSetup, so there is no esbuild enum downleveling to trip TS7022 and decorator metadata is still emitted. tsx version is now irrelevant to the tests, so the pin was dropped.) Drop each entry once its parent ships a range that resolves to >=0.28.1 on its own. Our own twenty-client-sdk raises its esbuild floor to ^0.28.1 directly in its package.json instead of via a resolution. googleapis/googleapis-common 8.0.1 -> singleton dedup for the googleapis 173 upgrade. googleapis-common 8.0.2 (published 2026-06-04, AFTER googleapis 173 on 2026-05-28) regressed its google-auth-library dep from a range to exact 10.5.0 (and gaxios to exact 7.1.3), while googleapis itself pulls google-auth-library ^10.2.0 (10.7.0); the two mismatched copies make OAuth2Client's type-identity diverge between the client our provider builds (via googleapis -> 10.7.0) and the one gmail/calendar method options expect (via googleapis-common -> 10.5.0), breaking every gmail/calendar service typecheck (TS2322/TS2769). The parents are already at latest (googleapis 173.0.0, googleapis-common 8.0.2) so we cannot fix by upgrading; instead we pin googleapis' googleapis-common back to 8.0.1, the last version with RANGE deps (google-auth-library ^10.1.0, gaxios ^7.0.0-rc.4) -- and the version googleapis 173 originally shipped against. Ranges resolve to the same hoisted versions googleapis uses, so google-auth-library AND gaxios both collapse to a single copy with no further resolution (a global google-auth-library pin would only dedup one of the two). Scoped to googleapis since it is the sole googleapis-common 8.x consumer. Drop once googleapis-common 8.0.3+ restores range deps or googleapis bumps to a common that does. js-yaml@npm:4.3.1 -> 4.3.2 -> GHSA-2883-xcg3-v3hh / CVE-2026-84375 (HIGH, maxTotalMergeKeys does not limit CPU use for empty merge sources, vulnerable >=4.0.0 <4.3.2, fixed 4.3.2; the 3.x line has its own 3.15.2 backport, which @istanbuljs/load-nyc-config's ^3.13.1 reaches on its own). The six @mintlify/* packages (cli, common, prebuild, previewing, scraping, validation) exact-pin js-yaml 4.3.1 and still do in the latest mintlify 4.2.892 / @mintlify/cli 4.0.1495, so no parent upgrade carries the fix; a single descriptor-keyed entry replaces six parent-scoped ones and touches only that exact 4.3.1 pin (every caret consumer dedupes onto 4.3.2 naturally). Their previous six pins had been dropped once the mintlify 4.2.816 lift brought a chain pinning 4.3.1 itself; drop once mintlify pins >=4.3.2. Of the two js-yaml 3.x consumers (both declaring ^3.13.1): @istanbuljs/[email protected] (via babel-plugin-istanbul coverage) is UNPINNED -- the 3.x line shipped backports for every js-yaml advisory (3.15.0 fixes GHSA-h67p-54hq-rp68 + GHSA-52cp-r559-cp3m, 3.15.1 fixes GHSA-5p4m-2wfm-xmqj), so it resolves a clean 3.15.1 within its own range, and as build-only coverage tooling that is enough. [email protected] (via mintlify in twenty-docs) stays FORCED to 4.3.2 (front-matter/js-yaml, lifted in step with the entry above) as a deliberate posture call: 4.x is the maintained js-yaml line, while the 3.x fixes were backports to a legacy major that future advisories may not get, and front-matter parses docs content. Because js-yaml 4.x removed the safeLoad API front-matter's default path calls, the companion patch (front-matter@npm:4.0.2 -> .yarn/patches/front-matter-npm-4.0.2-e1cc0efa69.patch) sets loader = parser.load (safe-by-default in 4.x); pin and patch are a matched pair -- the patch without the pin would select 3.x's UNSAFE full-schema load, so they must only ever be dropped together. The version move stays a separate resolution because a yarn patch only rewrites a package's files, not its resolved dependency graph. Drop both once mintlify moves front-matter off js-yaml 3.x or drops it. @react-email/ui/next 16.3.5 -> Next.js July-2026 security release (CVE-2026-64641 App-Router Server-Actions DoS, CVE-2026-64645 rewrites/redirects SSRF + open redirect, and the sibling CVE-2026-64642..64648), vulnerable >=16.0.0 <16.2.11, fixed 16.2.11; @react-email/ui 6.9.0 hard-pins next 16.2.6 exact (transitive via react-email in twenty-emails). The parent bump was ATTEMPTED and reverted: @react-email/ui + react-email ^6.9.2 do carry next 16.3.0, but that pulls a SECOND next (16.3.0 alongside twenty-website's 16.3.2) plus its dependency subtree into the lockfile -- the scoped pin here forces @react-email/ui's next to the version twenty-website already resolves within ^16.2.6 (16.3.5 since the September-2026 CRITICAL unauthenticated-RCE advisories GHSA-p293-qw3h-jr36 / CVE-2026-75604 on Windows-hosted servers and GHSA-2xp9-vwfh-vxw4 in the Image Optimization API with AVIF input, both >=16.0.0 <16.3.3, fixed 16.3.3), so it dedupes with ZERO new packages, which is the leaner outcome for a security PR. So @react-email/ui is held at ^6.9.0 with this scoped pin; drop once @react-email/ui itself depends on the next version twenty-website resolves. mintlify axios + adm-zip (twenty-docs) -> bumped mintlify ^4.2.594 -> ^4.2.790 (resolves 4.2.816), which pulls @mintlify/cli >=4.0.1393 -> adm-zip 0.6.0 (fixes CVE-2026-39244 / GHSA-xcpc-8h2w-3j85 for the @mintlify/cli + @mintlify/previewing copies) AND @mintlify/models >=0.0.347 -> axios 1.18.0 (fixes CVE-2026-44494 / SNYK-JS-AXIOS-17111079 axios prototype pollution via config.proxy, vulnerable >=1.15.2 <1.18.0). This one parent bump REPLACED three former scoped resolutions (@mintlify/models/axios, @mintlify/cli/adm-zip, @mintlify/previewing/adm-zip). Blast radius was measured and is contained: ~56 lockfile descriptors change, ALL inside twenty-docs' mintlify subtree (shiki/twoslash, remark/mdx, puppeteer 22->24, and a NESTED type-fest v5) -- the root-hoisted type-fest stays v4 (4.41.0) and every twenty-* workspace package declares type-fest 4.x, so type-fest v5 lives only inside mintlify's own nested tree and touches no workspace typecheck. All typechecks pass (twenty-front / -website / -emails / -ui / -shared reliably; twenty-server passes too modulo the pre-existing flaky tsgo 7.0.0-dev stack-overflow that hits ~1 run in 5 with ZERO type errors), and the mintlify CLI's harmless nested-React 'invalid hook call' warning is byte-identical before and after the bump. nx/axios 1.20.0 + @mintlify/models/axios 1.20.0 -> the September-2026 axios advisory batch, twelve advisories all fixed in 1.20.0, including the HIGH prototype-pollution gadgets GHSA-x97p-jq2g-jp4f / GHSA-m8m8-qj5v-23w3, the HTTP/2 DNS/proxy-control bypass GHSA-3pq3-5fj3-cg6v, the fetch-adapter maxRedirects bypass GHSA-r4gj-5m52-g5wh, the HTTP/2 unhandled-error DoS GHSA-542g-h47m-68v8 and the two ReDoS advisories GHSA-c29m-xwm3-cm6r / GHSA-mghh-pgcx-3jjj (vulnerable ranges vary per advisory, all <1.20.0). Every caret consumer (twenty-server + twenty-sdk ^1.16.0, and transitives) resolves 1.20.0 on its own; these two parents exact-pin a vulnerable axios in their LATEST releases, so no parent upgrade carries the fix: nx pins 1.18.1 through 22.7.12 and 23.2.1 alike, and @mintlify/models pins 1.18.0 through its latest 0.0.363 (mintlify 4.2.964). Both entries are RE-ADDITIONS of previously dropped pins (see below) now that the parents have fallen behind again; drop each once its parent ships axios >=1.20.0. (The former nx/axios pin had been dropped when nx 22.7.7+ moved to axios 1.18.1, >=1.18.0 -- sufficient for the old config.proxy advisory, not for this batch.) adm-zip -> 0.6.1 for the September-2026 adm-zip advisory batch, all vulnerable <=0.6.0 and fixed in 0.6.1: GHSA-8238-w5pm-2374 (HIGH, unhandled error event in async DEFLATE decompression crashes the process), GHSA-rcw4-f5rp-g42v (HIGH, the decompression-bomb guard added for CVE-2026-39244 can be bypassed), GHSA-j5f4-cc29-5x44 (HIGH, extraction preserves SUID/SGID bits from untrusted archives), GHSA-c6fg-446q-cg94 (getDataAsync() bypasses the maxOutputLength guard) and GHSA-p634-w6r4-rjp2 (duplicate entry names resolve inconsistently between getEntry() and extractAllTo()); 0.6.1 also still covers CVE-2026-39244 / GHSA-xcpc-8h2w-3j85 (unbounded Buffer.alloc from a declared uncompressed size, fixed 0.6.0) that the earlier 0.6.0 pins were added for. All FOUR consumers exact-pin a vulnerable adm-zip in their latest releases, so each keeps its OWN scoped pin (not a global one) with its own drop condition: @mintlify/cli and @mintlify/previewing pin 0.6.0 (still 0.6.0 in @mintlify/cli 4.0.1573 / @mintlify/previewing 4.0.1428, mintlify 4.2.970) -- these two entries are RE-ADDITIONS, dropped when the mintlify 4.2.816 lift brought 0.6.0, sufficient then but not for this batch; zapier-platform-cli pins 0.5.16 (still 0.5.16 in its latest 19.1.0, cf. its sibling zapier-platform-core/form-data + zapier-platform-cli/esbuild pins); @module-federation/dts-plugin 2.5.1 pins 0.5.10 (dts-plugin 2.9.2 moves to ^0.6.1, but @nx/module-federation 22.7.8 holds the module-federation stack at ^2.3.3 -> 2.5.1, so reaching it means forcing the whole build-critical module-federation runtime up or bumping all of nx to 23.x -- disproportionate, and it sits alongside the existing @module-federation/dts-plugin/undici pin for the same package and reason). 0.6.0 -> 0.6.1 is a patch release; the 0.6.0 major's breaking changes (extractEntryTo preserving subdirectories, engines Node >=14) were already absorbed by the zapier and dts-plugin pins, and the mintlify copies were already on 0.6.0. Drop the two mintlify pins once @mintlify/cli and @mintlify/previewing ship adm-zip >=0.6.1; drop the zapier pin once zapier-platform-cli does; drop the dts-plugin pin once @nx/module-federation carries module-federation >=2.9.2.",
"version": "0.2.1",
"nx": {},
"scripts": {
diff --git a/packages/twenty-apps/examples/document-generator/yarn.lock b/packages/twenty-apps/examples/document-generator/yarn.lock
index 8a115fdde6f..9584a1a0267 100644
--- a/packages/twenty-apps/examples/document-generator/yarn.lock
+++ b/packages/twenty-apps/examples/document-generator/yarn.lock
@@ -3021,9 +3021,9 @@ __metadata:
linkType: hard
"undici@npm:^6.25.0":
- version: 6.28.0
- resolution: "undici@npm:6.28.0"
- checksum: 10c0/3029a70df06b38b5b2f30732932a1e92544c753cd82c8abdf0d35afad48e0ba91612e79fe3a442dbbb9434d6a9eba2b714d5ea28984c903dda2b5d5444f38354
+ version: 6.29.0
+ resolution: "undici@npm:6.29.0"
+ checksum: 10c0/3fb2117985be977ba8b6bd6a242fec915e1b1d0f9681f5adb3f508fb1717352452d65bcfd3bed09e7c776cfda403a4e8edb24a318492f8b2d793439af2b8699b
languageName: node
linkType: hard
diff --git a/packages/twenty-apps/public/call-recorder/yarn.lock b/packages/twenty-apps/public/call-recorder/yarn.lock
index f1edeeb5de2..5ccedfa0b37 100644
--- a/packages/twenty-apps/public/call-recorder/yarn.lock
+++ b/packages/twenty-apps/public/call-recorder/yarn.lock
@@ -3736,9 +3736,9 @@ __metadata:
linkType: hard
"undici@npm:^6.25.0":
- version: 6.28.0
- resolution: "undici@npm:6.28.0"
- checksum: 10c0/3029a70df06b38b5b2f30732932a1e92544c753cd82c8abdf0d35afad48e0ba91612e79fe3a442dbbb9434d6a9eba2b714d5ea28984c903dda2b5d5444f38354
+ version: 6.29.0
+ resolution: "undici@npm:6.29.0"
+ checksum: 10c0/3fb2117985be977ba8b6bd6a242fec915e1b1d0f9681f5adb3f508fb1717352452d65bcfd3bed09e7c776cfda403a4e8edb24a318492f8b2d793439af2b8699b
languageName: node
linkType: hard
diff --git a/packages/twenty-apps/public/companion/yarn.lock b/packages/twenty-apps/public/companion/yarn.lock
index fe74f5f17d0..ecfaae28cea 100644
--- a/packages/twenty-apps/public/companion/yarn.lock
+++ b/packages/twenty-apps/public/companion/yarn.lock
@@ -3176,9 +3176,9 @@ __metadata:
linkType: hard
"undici@npm:^8.4.1":
- version: 8.10.2
- resolution: "undici@npm:8.10.2"
- checksum: 10c0/66d7fc69149207cab570d6abbc9e965b6afe1ae889a7d46945b431165c973d6a56f3dd8b70a856e7ae1e550b6366a1cde6f06e68640587f0dadca38de72995ee
+ version: 8.11.2
+ resolution: "undici@npm:8.11.2"
+ checksum: 10c0/106f6991178fb7562fd90cdec7993c5f807a9428682306091f0c4b27fc474ec291f868e29972c6252988bf061ad193df943b3b99e775be157a28d92bbb95699d
languageName: node
linkType: hard
diff --git a/packages/twenty-apps/public/discord/yarn.lock b/packages/twenty-apps/public/discord/yarn.lock
index 9858136723e..577c97a106a 100644
--- a/packages/twenty-apps/public/discord/yarn.lock
+++ b/packages/twenty-apps/public/discord/yarn.lock
@@ -2999,9 +2999,9 @@ __metadata:
linkType: hard
"undici@npm:^6.25.0":
- version: 6.28.0
- resolution: "undici@npm:6.28.0"
- checksum: 10c0/3029a70df06b38b5b2f30732932a1e92544c753cd82c8abdf0d35afad48e0ba91612e79fe3a442dbbb9434d6a9eba2b714d5ea28984c903dda2b5d5444f38354
+ version: 6.29.0
+ resolution: "undici@npm:6.29.0"
+ checksum: 10c0/3fb2117985be977ba8b6bd6a242fec915e1b1d0f9681f5adb3f508fb1717352452d65bcfd3bed09e7c776cfda403a4e8edb24a318492f8b2d793439af2b8699b
languageName: node
linkType: hard
diff --git a/packages/twenty-apps/public/exa/yarn.lock b/packages/twenty-apps/public/exa/yarn.lock
index 47f11acb87e..7682ff74c17 100644
--- a/packages/twenty-apps/public/exa/yarn.lock
+++ b/packages/twenty-apps/public/exa/yarn.lock
@@ -2971,9 +2971,9 @@ __metadata:
linkType: hard
"undici@npm:^6.25.0":
- version: 6.28.0
- resolution: "undici@npm:6.28.0"
- checksum: 10c0/3029a70df06b38b5b2f30732932a1e92544c753cd82c8abdf0d35afad48e0ba91612e79fe3a442dbbb9434d6a9eba2b714d5ea28984c903dda2b5d5444f38354
+ version: 6.29.0
+ resolution: "undici@npm:6.29.0"
+ checksum: 10c0/3fb2117985be977ba8b6bd6a242fec915e1b1d0f9681f5adb3f508fb1717352452d65bcfd3bed09e7c776cfda403a4e8edb24a318492f8b2d793439af2b8699b
languageName: node
linkType: hard
diff --git a/packages/twenty-apps/public/fathom/yarn.lock b/packages/twenty-apps/public/fathom/yarn.lock
index 482114b4e4d..0282da63653 100644
--- a/packages/twenty-apps/public/fathom/yarn.lock
+++ b/packages/twenty-apps/public/fathom/yarn.lock
@@ -2896,9 +2896,9 @@ __metadata:
linkType: hard
"undici@npm:^8.4.1":
- version: 8.10.0
- resolution: "undici@npm:8.10.0"
- checksum: 10c0/37ae2b1db8f65c3a003504e2040e96887b99f9db16ba07dcf49c37ed8b7f8c72f4452f2d46f52f7c9e49518fe8325e3b5e7e02ac3a2424886bd67d4b62a0ecab
+ version: 8.11.2
+ resolution: "undici@npm:8.11.2"
+ checksum: 10c0/106f6991178fb7562fd90cdec7993c5f807a9428682306091f0c4b27fc474ec291f868e29972c6252988bf061ad193df943b3b99e775be157a28d92bbb95699d
languageName: node
linkType: hard
diff --git a/packages/twenty-apps/public/fireflies/yarn.lock b/packages/twenty-apps/public/fireflies/yarn.lock
index 00e7f079bd7..73102bbec76 100644
--- a/packages/twenty-apps/public/fireflies/yarn.lock
+++ b/packages/twenty-apps/public/fireflies/yarn.lock
@@ -3784,9 +3784,9 @@ __metadata:
linkType: hard
"undici@npm:^6.25.0":
- version: 6.28.0
- resolution: "undici@npm:6.28.0"
- checksum: 10c0/3029a70df06b38b5b2f30732932a1e92544c753cd82c8abdf0d35afad48e0ba91612e79fe3a442dbbb9434d6a9eba2b714d5ea28984c903dda2b5d5444f38354
+ version: 6.29.0
+ resolution: "undici@npm:6.29.0"
+ checksum: 10c0/3fb2117985be977ba8b6bd6a242fec915e1b1d0f9681f5adb3f508fb1717352452d65bcfd3bed09e7c776cfda403a4e8edb24a318492f8b2d793439af2b8699b
languageName: node
linkType: hard
diff --git a/packages/twenty-apps/public/granola/yarn.lock b/packages/twenty-apps/public/granola/yarn.lock
index 55f6409f48c..6a7a9e8cfa5 100644
--- a/packages/twenty-apps/public/granola/yarn.lock
+++ b/packages/twenty-apps/public/granola/yarn.lock
@@ -3671,9 +3671,9 @@ __metadata:
linkType: hard
"undici@npm:^8.4.1":
- version: 8.10.1
- resolution: "undici@npm:8.10.1"
- checksum: 10c0/90ac5636aa9d22fb710a261ef05e136df6b4bd7a0122201796bd2eb59ccab6661cdf4f635e543ca04420379eafe3f4d214031bbc7623214287988881c24dad55
+ version: 8.11.2
+ resolution: "undici@npm:8.11.2"
+ checksum: 10c0/106f6991178fb7562fd90cdec7993c5f807a9428682306091f0c4b27fc474ec291f868e29972c6252988bf061ad193df943b3b99e775be157a28d92bbb95699d
languageName: node
linkType: hard
diff --git a/packages/twenty-apps/public/last-contact/yarn.lock b/packages/twenty-apps/public/last-contact/yarn.lock
index ac08ca3a5a7..f8554ae9c25 100644
--- a/packages/twenty-apps/public/last-contact/yarn.lock
+++ b/packages/twenty-apps/public/last-contact/yarn.lock
@@ -3252,9 +3252,9 @@ __metadata:
linkType: hard
"undici@npm:^6.25.0":
- version: 6.28.0
- resolution: "undici@npm:6.28.0"
- checksum: 10c0/3029a70df06b38b5b2f30732932a1e92544c753cd82c8abdf0d35afad48e0ba91612e79fe3a442dbbb9434d6a9eba2b714d5ea28984c903dda2b5d5444f38354
+ version: 6.29.0
+ resolution: "undici@npm:6.29.0"
+ checksum: 10c0/3fb2117985be977ba8b6bd6a242fec915e1b1d0f9681f5adb3f508fb1717352452d65bcfd3bed09e7c776cfda403a4e8edb24a318492f8b2d793439af2b8699b
languageName: node
linkType: hard
diff --git a/packages/twenty-apps/public/linear/yarn.lock b/packages/twenty-apps/public/linear/yarn.lock
index 6ea5ca150f4..d2454527b0b 100644
--- a/packages/twenty-apps/public/linear/yarn.lock
+++ b/packages/twenty-apps/public/linear/yarn.lock
@@ -2999,9 +2999,9 @@ __metadata:
linkType: hard
"undici@npm:^6.25.0":
- version: 6.28.0
- resolution: "undici@npm:6.28.0"
- checksum: 10c0/3029a70df06b38b5b2f30732932a1e92544c753cd82c8abdf0d35afad48e0ba91612e79fe3a442dbbb9434d6a9eba2b714d5ea28984c903dda2b5d5444f38354
+ version: 6.29.0
+ resolution: "undici@npm:6.29.0"
+ checksum: 10c0/3fb2117985be977ba8b6bd6a242fec915e1b1d0f9681f5adb3f508fb1717352452d65bcfd3bed09e7c776cfda403a4e8edb24a318492f8b2d793439af2b8699b
languageName: node
linkType: hard
diff --git a/packages/twenty-apps/public/people-data-labs/yarn.lock b/packages/twenty-apps/public/people-data-labs/yarn.lock
index d7f29afebe2..f32338dbd63 100644
--- a/packages/twenty-apps/public/people-data-labs/yarn.lock
+++ b/packages/twenty-apps/public/people-data-labs/yarn.lock
@@ -2926,9 +2926,9 @@ __metadata:
linkType: hard
"undici@npm:^6.25.0":
- version: 6.28.0
- resolution: "undici@npm:6.28.0"
- checksum: 10c0/3029a70df06b38b5b2f30732932a1e92544c753cd82c8abdf0d35afad48e0ba91612e79fe3a442dbbb9434d6a9eba2b714d5ea28984c903dda2b5d5444f38354
+ version: 6.29.0
+ resolution: "undici@npm:6.29.0"
+ checksum: 10c0/3fb2117985be977ba8b6bd6a242fec915e1b1d0f9681f5adb3f508fb1717352452d65bcfd3bed09e7c776cfda403a4e8edb24a318492f8b2d793439af2b8699b
languageName: node
linkType: hard
diff --git a/packages/twenty-apps/public/slack/yarn.lock b/packages/twenty-apps/public/slack/yarn.lock
index 5adfcaa555b..8e2464a7448 100644
--- a/packages/twenty-apps/public/slack/yarn.lock
+++ b/packages/twenty-apps/public/slack/yarn.lock
@@ -4198,9 +4198,9 @@ __metadata:
linkType: hard
"undici@npm:^6.25.0":
- version: 6.28.0
- resolution: "undici@npm:6.28.0"
- checksum: 10c0/3029a70df06b38b5b2f30732932a1e92544c753cd82c8abdf0d35afad48e0ba91612e79fe3a442dbbb9434d6a9eba2b714d5ea28984c903dda2b5d5444f38354
+ version: 6.29.0
+ resolution: "undici@npm:6.29.0"
+ checksum: 10c0/3fb2117985be977ba8b6bd6a242fec915e1b1d0f9681f5adb3f508fb1717352452d65bcfd3bed09e7c776cfda403a4e8edb24a318492f8b2d793439af2b8699b
languageName: node
linkType: hard
diff --git a/packages/twenty-apps/public/teams/yarn.lock b/packages/twenty-apps/public/teams/yarn.lock
index 742fb7c2928..9309e90e67a 100644
--- a/packages/twenty-apps/public/teams/yarn.lock
+++ b/packages/twenty-apps/public/teams/yarn.lock
@@ -4064,9 +4064,9 @@ __metadata:
linkType: hard
"undici@npm:^8.4.1":
- version: 8.10.2
- resolution: "undici@npm:8.10.2"
- checksum: 10c0/66d7fc69149207cab570d6abbc9e965b6afe1ae889a7d46945b431165c973d6a56f3dd8b70a856e7ae1e550b6366a1cde6f06e68640587f0dadca38de72995ee
+ version: 8.11.2
+ resolution: "undici@npm:8.11.2"
+ checksum: 10c0/106f6991178fb7562fd90cdec7993c5f807a9428682306091f0c4b27fc474ec291f868e29972c6252988bf061ad193df943b3b99e775be157a28d92bbb95699d
languageName: node
linkType: hard
diff --git a/yarn.lock b/yarn.lock
index f274f2ebdfe..89a6c8a8c5b 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -4760,10 +4760,10 @@ __metadata:
languageName: node
linkType: hard
-"@bufbuild/protobuf@npm:^2.12.1":
- version: 2.13.0
- resolution: "@bufbuild/protobuf@npm:2.13.0"
- checksum: 10c0/bb4d39512302887399355ac2ba1228e562c1cae818ff88b4b85b3060758aba5fec94786fe80f69de8878f98e730911c0bd145741adb582d0abf6b42de921e50c
+"@bufbuild/protobuf@npm:^2.14.1":
+ version: 2.16.0
+ resolution: "@bufbuild/protobuf@npm:2.16.0"
+ checksum: 10c0/ba3bc677e801a71d9cf0bdc138174144e493706efec3a47865eb07e956423315a80ff12301f6835d352202ae4d6599f2946a7c67338cf0079ed2a06af1a18097
languageName: node
linkType: hard
@@ -4874,50 +4874,50 @@ __metadata:
languageName: node
linkType: hard
-"@cloudflare/unenv-preset@npm:2.16.1":
- version: 2.16.1
- resolution: "@cloudflare/unenv-preset@npm:2.16.1"
+"@cloudflare/unenv-preset@npm:2.16.2":
+ version: 2.16.2
+ resolution: "@cloudflare/unenv-preset@npm:2.16.2"
peerDependencies:
unenv: 2.0.0-rc.24
workerd: ">1.20260305.0 <2.0.0-0"
peerDependenciesMeta:
workerd:
optional: true
- checksum: 10c0/08c9bd9ef488a14fd5330eb2c0829fc221f97f12295f8263dc8e3a6816ebd1a629e7255a3619b8bb688f1f58deafe28042c4e90ea84c926438c768f235f82ad9
+ checksum: 10c0/c8b9d1304e3679782ea113ec6403767ae55a108e18824f68b771c8764dfb47244cb68aa021ebfbb6cf3c3ae18570c5df3e3ca4158629f12725c01d3d74490fc4
languageName: node
linkType: hard
-"@cloudflare/workerd-darwin-64@npm:1.20260911.1":
- version: 1.20260911.1
- resolution: "@cloudflare/workerd-darwin-64@npm:1.20260911.1"
+"@cloudflare/workerd-darwin-64@npm:1.20260926.1":
+ version: 1.20260926.1
+ resolution: "@cloudflare/workerd-darwin-64@npm:1.20260926.1"
conditions: os=darwin & cpu=x64
languageName: node
linkType: hard
-"@cloudflare/workerd-darwin-arm64@npm:1.20260911.1":
- version: 1.20260911.1
- resolution: "@cloudflare/workerd-darwin-arm64@npm:1.20260911.1"
+"@cloudflare/workerd-darwin-arm64@npm:1.20260926.1":
+ version: 1.20260926.1
+ resolution: "@cloudflare/workerd-darwin-arm64@npm:1.20260926.1"
conditions: os=darwin & cpu=arm64
languageName: node
linkType: hard
-"@cloudflare/workerd-linux-64@npm:1.20260911.1":
- version: 1.20260911.1
- resolution: "@cloudflare/workerd-linux-64@npm:1.20260911.1"
+"@cloudflare/workerd-linux-64@npm:1.20260926.1":
+ version: 1.20260926.1
+ resolution: "@cloudflare/workerd-linux-64@npm:1.20260926.1"
conditions: os=linux & cpu=x64
languageName: node
linkType: hard
-"@cloudflare/workerd-linux-arm64@npm:1.20260911.1":
- version: 1.20260911.1
- resolution: "@cloudflare/workerd-linux-arm64@npm:1.20260911.1"
+"@cloudflare/workerd-linux-arm64@npm:1.20260926.1":
+ version: 1.20260926.1
+ resolution: "@cloudflare/workerd-linux-arm64@npm:1.20260926.1"
conditions: os=linux & cpu=arm64
languageName: node
linkType: hard
-"@cloudflare/workerd-windows-64@npm:1.20260911.1":
- version: 1.20260911.1
- resolution: "@cloudflare/workerd-windows-64@npm:1.20260911.1"
+"@cloudflare/workerd-windows-64@npm:1.20260926.1":
+ version: 1.20260926.1
+ resolution: "@cloudflare/workerd-windows-64@npm:1.20260926.1"
conditions: os=win32 & cpu=x64
languageName: node
linkType: hard
@@ -5082,22 +5082,22 @@ __metadata:
languageName: node
linkType: hard
-"@connectrpc/connect-web@npm:^2.1.2":
- version: 2.1.2
- resolution: "@connectrpc/connect-web@npm:2.1.2"
+"@connectrpc/connect-web@npm:^2.2.0":
+ version: 2.2.0
+ resolution: "@connectrpc/connect-web@npm:2.2.0"
peerDependencies:
"@bufbuild/protobuf": ^2.7.0
- "@connectrpc/connect": 2.1.2
- checksum: 10c0/304667186990d79e61ace8af03a39c5474e6ecb21282eeaa9e216a0e214524003891005ff3cfbda33230c21b779cfece530bf8cfdd48550b7861621513d18e0e
+ "@connectrpc/connect": 2.2.0
+ checksum: 10c0/ad98062fc5e9a027a917487d9abcab64dccfc8bbb357e78172be787d669f7b611e6ccd75148633c1b874222060f803f2ae4a5ae72c2708a84658dc9786b2d958
languageName: node
linkType: hard
-"@connectrpc/connect@npm:^2.1.2":
- version: 2.1.2
- resolution: "@connectrpc/connect@npm:2.1.2"
+"@connectrpc/connect@npm:^2.2.0":
+ version: 2.2.0
+ resolution: "@connectrpc/connect@npm:2.2.0"
peerDependencies:
"@bufbuild/protobuf": ^2.7.0
- checksum: 10c0/4e1500089023b752efd44fa940a5ae1e1fa00e1bebc4ba0ced272bb935920d8c3b85b77450e644ad442bb8ca9a275b0c17136f896ba8eff036178131db01d615
+ checksum: 10c0/f03a5a8c74d74a9016027280173f44d983f69e9b999dcad47520c2dd474be2289bd33b22e1e374173dc919c6ffb1ab5886464d6c279bca26ff2432231bdf0915
languageName: node
linkType: hard
@@ -29882,25 +29882,25 @@ __metadata:
linkType: hard
"e2b@npm:^2.39.0":
- version: 2.45.0
- resolution: "e2b@npm:2.45.0"
+ version: 2.51.0
+ resolution: "e2b@npm:2.51.0"
dependencies:
- "@bufbuild/protobuf": "npm:^2.12.1"
- "@connectrpc/connect": "npm:^2.1.2"
- "@connectrpc/connect-web": "npm:^2.1.2"
+ "@bufbuild/protobuf": "npm:^2.14.1"
+ "@connectrpc/connect": "npm:^2.2.0"
+ "@connectrpc/connect-web": "npm:^2.2.0"
chalk: "npm:^5.3.0"
compare-versions: "npm:^6.1.0"
dockerfile-ast: "npm:^0.7.1"
glob: "npm:^13.0.6"
openapi-fetch: "npm:^0.14.1"
platform: "npm:^1.3.6"
- tar: "npm:^7.5.19"
- undici: "npm:^7.29.0"
- undici8: "npm:[email protected]"
+ tar: "npm:^7.5.22"
+ undici: "npm:^7.29.1"
+ undici8: "npm:[email protected]"
dependenciesMeta:
undici8:
optional: true
- checksum: 10c0/f171bf07ea115fbfa1ab21f1cb749361fd57a7a313012988860972fac13309eb2ae20090256263debd9b15cf24f7308ba42904a653d139e4b62b841a0cf0543b
+ checksum: 10c0/b5d62b8f11ca94781cccadcc9212891ee9e670c434f24997a4ebe579f31165a24b9d05a450571ae46238f25722ff34cc9a75406abae6bb97beed6f0e5f1d1380
languageName: node
linkType: hard
@@ -39903,17 +39903,17 @@ __metadata:
languageName: node
linkType: hard
-"miniflare@npm:5.20260911.0-alpha":
- version: 5.20260911.0-alpha
- resolution: "miniflare@npm:5.20260911.0-alpha"
+"miniflare@npm:5.20260926.1-alpha":
+ version: 5.20260926.1-alpha
+ resolution: "miniflare@npm:5.20260926.1-alpha"
dependencies:
"@cspotcode/source-map-support": "npm:0.8.1"
sharp: "npm:0.35.4"
- undici: "npm:7.29.0"
- workerd: "npm:1.20260911.1"
+ undici: "npm:7.29.1"
+ workerd: "npm:1.20260926.1"
ws: "npm:8.21.0"
youch: "npm:4.1.0-beta.10"
- checksum: 10c0/f04715039abc54e616916268e78ed7634224bb8e10e20955c8724da7b4412dd35f01e2da97990bffbd949252a40da8fa93fc2caa03e8deab20bdda28d2c06b62
+ checksum: 10c0/a506aef74420d06ad1b16cee96ea4dd29851cb34793dc100d43d60224e030cfd7a2668d31965d3d49cb907651a7ab4147afb80b075e124d3e3c1ef4ec7ef5698
languageName: node
linkType: hard
@@ -49395,7 +49395,7 @@ __metadata:
languageName: node
linkType: hard
-"tar@npm:^7.5.19":
+"tar@npm:^7.5.22":
version: 7.5.22
resolution: "tar@npm:7.5.22"
dependencies:
@@ -51595,38 +51595,38 @@ __metadata:
languageName: node
linkType: hard
-"undici8@npm:[email protected]":
- version: 8.10.0
- resolution: "undici@npm:8.10.0"
- checksum: 10c0/37ae2b1db8f65c3a003504e2040e96887b99f9db16ba07dcf49c37ed8b7f8c72f4452f2d46f52f7c9e49518fe8325e3b5e7e02ac3a2424886bd67d4b62a0ecab
+"undici8@npm:[email protected]":
+ version: 8.10.2
+ resolution: "undici@npm:8.10.2"
+ checksum: 10c0/66d7fc69149207cab570d6abbc9e965b6afe1ae889a7d46945b431165c973d6a56f3dd8b70a856e7ae1e550b6366a1cde6f06e68640587f0dadca38de72995ee
languageName: node
linkType: hard
-"undici@npm:7.29.0, undici@npm:^7.29.0":
- version: 7.29.0
- resolution: "undici@npm:7.29.0"
- checksum: 10c0/85ea96e91e7f3de24de678cbbc54230fdd641a3b0643005f2aef044af1f1a2db8fbecb88b28e6fa78bb41ffeafda4479b57075b6b6ab92beac4b7b5ab53f9b10
+"undici@npm:7.29.1":
+ version: 7.29.1
+ resolution: "undici@npm:7.29.1"
+ checksum: 10c0/5a419b1364531071ebdfd93748f7f2392d4eb6d68dd99814e1020f8fc6a517e3298129004c871516ee204bac68aba93541f587200b04a7449b8d45683a7d86f6
languageName: node
linkType: hard
"undici@npm:^6.25.0":
- version: 6.28.0
- resolution: "undici@npm:6.28.0"
- checksum: 10c0/3029a70df06b38b5b2f30732932a1e92544c753cd82c8abdf0d35afad48e0ba91612e79fe3a442dbbb9434d6a9eba2b714d5ea28984c903dda2b5d5444f38354
+ version: 6.29.0
+ resolution: "undici@npm:6.29.0"
+ checksum: 10c0/3fb2117985be977ba8b6bd6a242fec915e1b1d0f9681f5adb3f508fb1717352452d65bcfd3bed09e7c776cfda403a4e8edb24a318492f8b2d793439af2b8699b
languageName: node
linkType: hard
-"undici@npm:^7.24.4":
- version: 7.29.1
- resolution: "undici@npm:7.29.1"
- checksum: 10c0/5a419b1364531071ebdfd93748f7f2392d4eb6d68dd99814e1020f8fc6a517e3298129004c871516ee204bac68aba93541f587200b04a7449b8d45683a7d86f6
+"undici@npm:^7.24.4, undici@npm:^7.29.0, undici@npm:^7.29.1":
+ version: 7.30.0
+ resolution: "undici@npm:7.30.0"
+ checksum: 10c0/011a321a9198532b0f0504740faa43b9ab8fcc0e4f60104e5c9cb808a61faeb03e4be4aec4f0c65f47913d7c7d9d91591793a6cb9ab843f98ca2c3d711c4a34c
languageName: node
linkType: hard
"undici@npm:^8.4.1, undici@npm:^8.9.0":
- version: 8.9.0
- resolution: "undici@npm:8.9.0"
- checksum: 10c0/e3d9fa35a9aa8360d9f56e66bd372f451ee053e25066a97fd9fab3816267035660f67870c6d709a58a5411551657af78c4475be5b31c113b04f70251309900d0
+ version: 8.11.2
+ resolution: "undici@npm:8.11.2"
+ checksum: 10c0/106f6991178fb7562fd90cdec7993c5f807a9428682306091f0c4b27fc474ec291f868e29972c6252988bf061ad193df943b3b99e775be157a28d92bbb95699d
languageName: node
linkType: hard
@@ -53484,15 +53484,15 @@ __metadata:
languageName: node
linkType: hard
-"workerd@npm:1.20260911.1":
- version: 1.20260911.1
- resolution: "workerd@npm:1.20260911.1"
+"workerd@npm:1.20260926.1":
+ version: 1.20260926.1
+ resolution: "workerd@npm:1.20260926.1"
dependencies:
- "@cloudflare/workerd-darwin-64": "npm:1.20260911.1"
- "@cloudflare/workerd-darwin-arm64": "npm:1.20260911.1"
- "@cloudflare/workerd-linux-64": "npm:1.20260911.1"
- "@cloudflare/workerd-linux-arm64": "npm:1.20260911.1"
- "@cloudflare/workerd-windows-64": "npm:1.20260911.1"
+ "@cloudflare/workerd-darwin-64": "npm:1.20260926.1"
+ "@cloudflare/workerd-darwin-arm64": "npm:1.20260926.1"
+ "@cloudflare/workerd-linux-64": "npm:1.20260926.1"
+ "@cloudflare/workerd-linux-arm64": "npm:1.20260926.1"
+ "@cloudflare/workerd-windows-64": "npm:1.20260926.1"
dependenciesMeta:
"@cloudflare/workerd-darwin-64":
optional: true
@@ -53506,25 +53506,25 @@ __metadata:
optional: true
bin:
workerd: bin/workerd
- checksum: 10c0/6903641bd5a2e997f6ddde7dda8c84facabdd3bf6c3832e3d7278d4e18810016f9883228d6bae16318bebfc086120204cdb9d2b3ebb628244693b8b493cb6490
+ checksum: 10c0/972bdae7d6ef8207a4b2258bcadb3e7374c4f398e506ef05b533ada515ffab4284bad27192a8b689981c1f801d8b09d5c300f62e659091f3c34d8e653d257d11
languageName: node
linkType: hard
"wrangler@npm:^4.0.0":
- version: 4.131.1
- resolution: "wrangler@npm:4.131.1"
+ version: 4.144.0
+ resolution: "wrangler@npm:4.144.0"
dependencies:
"@cloudflare/kv-asset-handler": "npm:0.5.0"
- "@cloudflare/unenv-preset": "npm:2.16.1"
+ "@cloudflare/unenv-preset": "npm:2.16.2"
blake3-wasm: "npm:2.1.5"
esbuild: "npm:0.28.1"
fsevents: "npm:2.3.3"
- miniflare: "npm:5.20260911.0-alpha"
+ miniflare: "npm:5.20260926.1-alpha"
path-to-regexp: "npm:6.3.0"
unenv: "npm:2.0.0-rc.24"
- workerd: "npm:1.20260911.1"
+ workerd: "npm:1.20260926.1"
peerDependencies:
- "@cloudflare/workers-types": ^5.20260911.1
+ "@cloudflare/workers-types": ^5.20260926.1
dependenciesMeta:
fsevents:
optional: true
@@ -53535,7 +53535,7 @@ __metadata:
cf-wrangler: bin/cf-wrangler.js
wrangler: bin/wrangler.js
wrangler2: bin/wrangler.js
- checksum: 10c0/bd63682dedf9b1bdd7cc08d7f15c3d90a3a8435f4432b4ce4dc0f390f6692cc0eb74640490fac1c2b8dc2d61d47ca42158b997009cfc5c28cee30e6ce2dc9e56
+ checksum: 10c0/0e3d36a7841bf61744229a3e521eeae3a0979c43a4685a131cf20f9ed1d94834c3d4f7c720c5901c60916e8a01b8c5463e10b83c8ccd03f3fbfb6c7db88559a3
languageName: node
linkType: hard