From 85e15e47334a4709e334b3f38d25f7f73bd4c694 Mon Sep 17 00:00:00 2001 From: Kyle Hoehns <9507268+kylehoehns@users.noreply.github.com> Date: Wed, 9 Sep 2026 09:36:54 -0500 Subject: [PATCH] chore: skip TypeScript 7.0 in Renovate until 7.1 ships an API TypeScript 7.0 is the native (tsgo) port and deliberately shipped with no programmatic compiler API. Its entire JS export surface is `version` and `versionMajorMinor`, so every tool built on the old API breaks: - typescript-eslint throws at import time, failing `pnpm lint` - ts-jest declares peer `typescript: >=4.3 <7`, which would fail `pnpm test` next Both maintainers have said they are waiting on the API expected in TS 7.1, and typescript-eslint has locked its thread in the meantime. Use `<7.0.0 || >=7.1.0` rather than a flat `<7` so the upgrade flows again on its own once 7.1 is released. The range excludes 7.1.0-dev prereleases, so this will not pull nightlies. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_019dUo24dvyCizU9GbU9dTww --- renovate.json | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/renovate.json b/renovate.json index c71aa574..a30da14e 100644 --- a/renovate.json +++ b/renovate.json @@ -11,6 +11,11 @@ { "matchUpdateTypes": ["minor", "patch", "pin", "digest"], "automerge": true + }, + { + "description": "TypeScript 7.0 shipped without a programmatic compiler API, so typescript-eslint and ts-jest both fail hard on it. Their maintainers are waiting for the API that TypeScript 7.1 is expected to ship. Allow 6.x and 7.1+, skip 7.0.x. See https://github.com/typescript-eslint/typescript-eslint/issues/10940 and https://github.com/kulshekhar/ts-jest/issues/5366 - remove this rule once both are resolved.", + "matchPackageNames": ["typescript"], + "allowedVersions": "<7.0.0 || >=7.1.0" } ], "schedule": ["* * 1 * *"],