# Keep TypeScript on 6.x until both sides of the build toolchain support 7.x: # vue-tsc currently imports the removed `typescript/lib/tsc` subpath, while # @nuxtjs/i18n's compile-time source analysis reaches # @typescript-eslint/typescript-estree, whose peer range still excludes TS 7. # The parser is build-only and is not copied into the production runner. Do not # upgrade TypeScript in isolation merely because `pnpm outdated` advertises 7.x. packages: - "packages/*" # Installation/postinstall owns vendor builds. Running lint must never implicitly reinstall and # rebuild all workspace packages via pnpm's default verifyDepsBeforeRun=install behavior. verifyDepsBeforeRun: false minimumReleaseAgeExcludePrune: true allowBuilds: "@parcel/watcher": true better-sqlite3: true cpu-features: true esbuild: true maplibre-gl: false ssh2: true vue-demi: true minimumReleaseAgeExclude: # Reviewed upgrade set. Keep exceptions version-specific so later releases still observe pnpm's # release-age policy; frozen installs in Docker must accept the same lockfile as local installs. - "emf-converter@4.11.2" - "@nuxt/kit@4.6.0" - "@ai-sdk/gateway@4.0.116" - "@ai-sdk/provider-utils@5.0.62" - "@ai-sdk/provider@4.0.29" - "@lucide/vue@1.59.0" - "@nuxt/kit@4.6.2" - "@nuxt/nitro-server@4.6.2" - "@nuxt/schema@4.6.2" - "@nuxt/vite-builder@4.6.2" - "@nuxt/vite-server@4.6.2" - "@tanstack/virtual-core@3.19.6" - "@tanstack/vue-virtual@3.13.47" - "@turbo/darwin-64@2.11.9" - "@turbo/darwin-arm64@2.11.9" - "@turbo/linux-64@2.11.9" - "@turbo/linux-arm64@2.11.9" - "@turbo/windows-64@2.11.9" - "@turbo/windows-arm64@2.11.9" - "ai@7.0.143" - "cssnano@9.9.0" - "dockview-core@8.6.0" - "dockview@8.6.0" - "dockview-vue@8.6.0" - "nuxt@4.6.2" - "turbo@2.11.9" overrides: # Nitro 2 still uses H3 1's event/response APIs; H3 2 requires Nitro 3. Keep the application's # direct H3 version aligned with Nuxt's runtime instead of mixing two incompatible event APIs. # CrossWS 0.4 supplies the binary-message API used by our shared terminal transport. crossws: 0.4.12 # Open File Viewer still requests EMF 3, which statically imports Node-only canvas bindings. # EMF 4 exposes a real browser condition and retains convertMetafileToDataUrl's options API. # Select that upstream browser implementation instead of maintaining aliases or native stubs. emf-converter: 4.11.2 # The plugin's default range remains on KaTeX 0.18. Keep its renderer and our 0.19 CSS/fonts # on the same release; the public renderToString API is unchanged by the strict-mode update. "@mdit/plugin-katex>katex": 0.19.0