chore(deps): update dependency typescript to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	^6.0.3 → ^7.0.2

---

Release Notes

microsoft/TypeScript (typescript)

v7.0.2

Compare Source

---

Configuration

📅 Schedule: (in timezone Europe/London)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @swc-node/register@1.12.1
npm error Found: typescript@7.0.2
npm error node_modules/typescript
npm error   dev typescript@"^7.0.2" from the root project
npm error   peer typescript@">=4.8.4" from ts-api-utils@2.5.0
npm error   node_modules/ts-api-utils
npm error     ts-api-utils@"^2.5.0" from @typescript-eslint/eslint-plugin@8.65.0
npm error     node_modules/@typescript-eslint/eslint-plugin
npm error       dev @typescript-eslint/eslint-plugin@"^8.65.0" from the root project
npm error     ts-api-utils@"^2.5.0" from @typescript-eslint/type-utils@8.65.0
npm error     node_modules/@typescript-eslint/type-utils
npm error       @typescript-eslint/type-utils@"8.65.0" from @typescript-eslint/eslint-plugin@8.65.0
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         dev @typescript-eslint/eslint-plugin@"^8.65.0" from the root project
npm error     1 more (@typescript-eslint/typescript-estree)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">= 4.3 < 7" from @swc-node/register@1.12.1
npm error node_modules/@swc-node/register
npm error   dev @swc-node/register@"^1.12.1" from the root project
npm error
npm error Conflicting peer dependency: typescript@6.0.3
npm error node_modules/typescript
npm error   peer typescript@">= 4.3 < 7" from @swc-node/register@1.12.1
npm error   node_modules/@swc-node/register
npm error     dev @swc-node/register@"^1.12.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-08-06T00_57_09_958Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-08-06T00_57_09_958Z-debug-0.log

[jonmattgray]

https://digicatapult.atlassian.net/browse/ENG-322

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[Ellenn-A]

Nice work on the TS6/7 side-by-side setup — verified locally that npm run check runs TS 7.0.2, typescript-eslint still resolves typescript to the 6.0.3 compatibility package, and lint/test/build/depcheck all pass. Two follow-ups worth considering before (or shortly after) merge:

1. CI doesn't actually run tsc

.github/workflows/test.yml and .github/workflows/release.yml both have:

matrix_commands: '["lint", "depcheck"]'

npm run check isn't in there, and tests-npm.yml only runs npm run test (mocha). This is pre-existing — we weren't running tsc in CI on TS6 either — but the TS7 migration makes it more visible: we've installed tsc-native specifically to type-check, and nothing on CI exercises it. ncc build uses swc, so it won't catch type errors either.

Suggested change in both workflows:

matrix_commands: '["lint", "depcheck", "check"]'

Not a blocker for this PR, but probably worth a quick follow-up so the TS7 upgrade actually produces CI signal.

2. Nothing explains why there are two TypeScripts

Right now the only trace of the strategy is these two lines in package.json:

"tsc-native": "npm:typescript@^7.0.2",
"typescript": "npm:@typescript/typescript6@^6.0.2"

Someone unfamiliar with the TS6/7 transition (or a future Renovate PR reviewer) is very likely to read "typescript": "npm:@typescript/typescript6@..." as an accidental downgrade and "clean it up" — which would silently break typescript-eslint, whose peer range is >=4.8.4 <6.1.0 and needs the TS6 compiler API.

Could we add a short note to the README, something like:

TypeScript 6 + 7 side-by-side

tsc runs TypeScript 7 (via the tsc-native alias). The typescript entry is aliased to @typescript/typescript6, Microsoft's TS6 compatibility package, because typescript-eslint still requires the TS6 compiler API (peer range <6.1.0). Once typescript-eslint supports TS7, drop the typescript alias and tsc-native, and reinstate a single "typescript": "^7" devDependency.

Optionally a one-liner comment above the deps too, so it's visible without leaving package.json.

Neither of these blocks the migration — the setup itself looks correct. Happy to open follow-up PRs for either if that's easier.