Update npm package typescript to v6

[hash-worker]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	5.9.3 → 6.0.3

---

Warning

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

---

Release Notes

microsoft/TypeScript (typescript)

v6.0.3: TypeScript 6.0.3

Compare Source

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

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).
• fixed issues query for TypeScript 6.0.3 (Stable).

Downloads are available on:

• npm

v6.0.2: TypeScript 6.0

Compare Source

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

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).

Downloads are available on:

• npm

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 4am every weekday,every weekend"
• Automerge
  • "before 4am every weekday,every weekend"

🚦 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 these updates again.

---

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

---

This PR has been generated by Mend Renovate.

[hash-worker]

⚠️ 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: yarn.lock

error This project's package.json defines "packageManager": "yarn@4.16.0". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hash	Error		Jul 11, 2026 11:37am
hashdotdesign-tokens	Error		Jul 11, 2026 11:37am
petrinaut	Error	Comment	Jul 11, 2026 11:37am

[cursor]

PR Summary

Medium Risk
A major TypeScript release applied repo-wide can surface new type errors or tooling incompatibilities (ESLint, codegen, webpack) even though the diff is dependency-only; CI and full builds are the main validation gate.

Overview
Bumps the typescript npm package from 5.9.3 to 6.0.3 across the Yarn workspace, touching apps (API, frontend, workers, MCP servers, browser plugin), shared libs, and integration test packages.

Each change is a package.json version pin only—no tsconfig, source, or lockfile edits appear in this diff. Several packages list typescript in both dependencies and devDependencies (e.g. hash-api, hash-ai-worker-ts, @blockprotocol/graph, @local/status); all of those entries move to 6.0.3.

After merge, expect tsc, lint:tsc, and build pipelines that compile TypeScript to run against the TypeScript 6 compiler everywhere those packages are used.

^{Reviewed by Cursor Bugbot for commit 5597289. Bugbot is set up for automated code reviews on this repo. Configure here.}