Skip to content

chore(deps): update dependency typescript to v7 - #771

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/typescript-7.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/typescript-7.x

Conversation

@renovate

@renovate renovate Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
typescript (source) ^5.9.3 → ^7.0.0 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

microsoft/TypeScript (typescript)

v7.0.2: TypeScript 7.0.2

Compare Source

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

v6.0.3: TypeScript 6.0.3

Compare Source

For release notes, check out the release announcement blog post.

Downloads are available on:

v6.0.2: TypeScript 6.0

Compare Source

For release notes, check out the release announcement blog post.

Downloads are available on:


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 9am on tuesday"
  • Automerge
    • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

@renovate
renovate Bot force-pushed the renovate/typescript-7.x branch from 8b916dd to a1683dd Compare October 6, 2026 10:52
@renovate
renovate Bot force-pushed the renovate/typescript-7.x branch from a1683dd to 9eea8e8 Compare October 6, 2026 21:58
@futo-kritika

futo-kritika Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Re-runKritika Review

Updates the shared TypeScript dependency to version 7.

1 finding · 1 blocking

Confidence 2/5 · high risk: The blocking finding at pnpm-workspace.yaml:129 is that TypeScript 7 no longer exposes the JS compiler API that ts-node 10.9.2 needs, so the start and sync:openapi scripts would fail. This is also a major-version bump of a shared build toolchain dependency, and typescript-eslint and ts-loader may be affected as well.

Findings

Summary

The change upgrades the workspace catalog and lockfile to TypeScript 7.0.2. That replaces the legacy JavaScript compiler API while the orchestration API still runs through ts-node 10.9.2, breaking its startup and OpenAPI synchronization scripts. The native compiler needs to be isolated or its API consumers migrated before replacing the shared dependency.

Sources consulted

Commands offered: curl, fd, gh, jq, rg, yq; run: gh, curl, rg.
1 diff file(s) left out of the prompt to fit its budget: pnpm-lock.yaml.

Reviews (1) · Last reviewed commit: "chore(deps): update dependency typescrip..." · kritika with openai/gpt-6.1-sol

Comment thread pnpm-workspace.yaml
tsconfig-paths: ^4.2.0
tsx: ^4.20.6
typescript: ^5.9.3
typescript: ^7.0.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[blocking · correctness] Keep the legacy compiler available for ts-node

TypeScript 7 is not a drop-in replacement for the JavaScript compiler API used by the retained tooling. At the 7.0.2 release tag, the published package's root export is lib/version.cjs, which exposes only version and versionMajorMinor; the packaging code preserves that export. In contrast, ts-node 10.9.2 loads typescript and immediately reads ts.sys.fileExists and ts.sys.readFile when loading configuration. Consequently, the orchestration API's start and sync:openapi scripts now fail during ts-node initialization rather than executing their entry points. Keep the shared catalog on the legacy compiler until its API consumers are migrated, or introduce the native compiler separately.

Suggested fix

Restore the shared TypeScript catalog to ^5.9.3 and regenerate the lockfile. If adopting the native CLI now, isolate it from dependencies that still require the legacy TypeScript compiler API.

Suggested change
typescript: ^7.0.0
typescript: ^5.9.3
Prompt for a coding agent
In pnpm-workspace.yaml at line 129, restore catalog.typescript to ^5.9.3 and regenerate pnpm-lock.yaml so compiler-API consumers resolve TypeScript 5 again. The TypeScript 7 package exports only version information at its root, whereas the retained ts-node 10.9.2 requires ts.sys and the legacy compiler API. Defer the shared-catalog upgrade until those consumers have been migrated, or isolate the native compiler in a separate opt-in dependency without replacing their TypeScript dependency.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants