build(deps-dev): bump typescript from 6.0.3 to 7.0.2 in the npm-dependencies group across 1 directory

[dependabot]

Bumps the npm-dependencies group with 1 update in the / directory: typescript.

Updates typescript from 6.0.3 to 7.0.2

Release notes

Sourced from typescript's releases.

TypeScript 7.0.2

https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/

This tag was originally released at: https://github.com/microsoft/typescript-go/releases/tag/typescript%2Fv7.0.2

Commits

• 1e4744d Merge branch 'main' into ts7-release
• a5a219cmicrosoft/typescript-go#4558
• ecfe30d Update status localization
• 5de25b5 Hide executable name in TypeScript status
• d7ce74a Show bundled TypeScript version for packaged servers
• 29be66a Correct TS 7 release version to 7.0.2
• ed2bd1b Merge branch 'main' into ts7-release
• 8873075 Bump the github-actions group across 1 directory with 3 updates (microsoft/ty...
• 9427131 Set up stable / nightly extension split, other prep (microsoft/typescript-go#...
• d4eaca5microsoft/typescript-go#4549
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.

[github-actions]

This is a Dependabot major-version bump of typescript (6.0.3 → 7.0.2) with no other code changes — package.json/package-lock.json only.

Should fix

• 🟠 package.json:38 — the new typescript version appears to be the Go-rewritten compiler (typescript-go), and the lockfile shows several @typescript-eslint/* packages still peer-pinned to typescript: ">=4.8.4 <6.1.0". Nothing proves this is actually broken, but it's unverified against this repo's lint/typecheck scripts, and I don't have visibility into this PR's CI status. See the inline comment for the detail.

Title and description are accurate and complete (Dependabot's own generated body) — no changes made there.

I could not check whether CI (typecheck/lint/format jobs) actually passed on this commit; I have no tool access to workflow run status in this session. That's the one thing I'd want confirmed before merge given the finding above. As a major-version bump, this shouldn't auto-merge under the repository's own default DEPENDABOT_AUTOMERGE_LEVELS (patch,minor) regardless of this review's outcome.

[github-actions]

🟠 Should fix [stack-default] — This bumps typescript across a major version boundary onto what release notes indicate is the Go-rewritten compiler (the PR body links microsoft/typescript-go's own release tag, and the bundled commits — "Show bundled TypeScript version for packaged servers", "Hide executable name in TypeScript status" — read as typescript-go/language-server work, not the classic tsc). package-lock.json backs this up: the typescript entry now pulls in a full set of @typescript/typescript-<platform>-<arch> optional dependencies (e.g. @typescript/typescript-netbsd-arm64), consistent with a native-binary distribution rather than the pure-JS compiler this repo has run until now.

That matters here because @typescript-eslint/eslint-plugin, @typescript-eslint/parser, @typescript-eslint/typescript-estree, @typescript-eslint/utils, and @typescript-eslint/type-utils all still declare "typescript": ">=4.8.4 <6.1.0" as a peer dependency (see the nested node_modules/typescript-eslint/node_modules/@typescript-eslint/* entries the lockfile diff adds) — they explicitly don't claim support even for 6.1+, let alone 7.x. Since there's only one typescript package in the tree and no nested copy satisfying that range, every one of these packages will resolve require("typescript") to 7.0.2 at runtime regardless of what their peerDependencies say. npm run lint doesn't use type-aware linting here (eslint.config.ts only extends tseslint.configs.recommended, no parserOptions.project), so the blast radius is bounded to typescript-estree's AST/syntax parsing rather than full type-checker use — but npm run typecheck runs tsc directly, which is now the new compiler binary end-to-end against this exact tsconfig.json.

None of this is necessarily broken — Microsoft may well have kept the classic JS API surface for compatibility during the transition — but it's unverified: typescript-eslint's own peer range says it hasn't been tested against this, and I don't have access to this PR's CI results to confirm lint/typecheck are actually green on this commit. Given DEPENDABOT_AUTOMERGE_LEVELS defaults to patch,minor (this is a major bump), this won't auto-merge regardless, but I'd hold it for a human to confirm CI is genuinely green — and ideally wait for typescript-eslint to widen its peer range for TS7 — before merging, rather than treating a clean review as sufficient here.