Bump typescript from 6.0.3 to 7.0.2

[dependabot]

Bumps typescript from 6.0.3 to 7.0.2.

Commits

• See full diff in compare view

Maintainer changes

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

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
omega-website-5xmp	Error		Aug 6, 2026 8:14am

[PatrickRose]

Blocked by the same family of upstream cap as the recurring eslint major-bump issue (see #1050): eslint-config-next@16.2.7 depends on typescript-eslint@^8.46.0 (resolves to 8.64.0), which pins its typescript peer range to ">=4.8.4 <6.1.0". typescript@7.0.2 falls outside that range, so npm ci fails with an ERESOLVE conflict:

npm error While resolving: typescript-eslint@8.64.0
npm error Found: typescript@7.0.2
npm error Could not resolve dependency:
npm error peer typescript@">=4.8.4 <6.1.0" from typescript-eslint@8.64.0

Checked npm today: typescript-eslint@latest is still 8.64.0 with the same <6.1.0 cap, so this isn't a rebase/CI flake — it needs typescript-eslint (or eslint-config-next's pin of it) to widen its typescript peer range before this can merge. Holding until then; no fix available on our side.

---

Generated by Claude Code

[PatrickRose]

Re-checked after today's rebase (new head eba26a8, package-lock refresh only — same target version 7.0.2): typescript-eslint@latest is now 8.65.0 but its peer range is still >=4.8.4 <6.1.0, so the block from the previous diagnosis still applies (Vercel deploy already fails on this commit for the same reason). Holding, no action needed.

---

Generated by Claude Code

[PatrickRose]

Re-checked after today's rebase (new head 23142a1, package-lock refresh only — same target version 7.0.2): typescript-eslint@latest is still 8.65.0 with peer range >=4.8.4 <6.1.0, so the block from the previous diagnosis (#1044 (comment)) still applies. Holding, no action needed.

---

Generated by Claude Code

[PatrickRose]

Re-checked after today's rebase (new head a3b5d36, package-lock refresh only — same target version 7.0.2): typescript-eslint@latest is still 8.65.0 with peer range >=4.8.4 <6.1.0, so the block from the previous diagnosis (#1044 (comment)) still applies. Vercel deploy fails the same way. Holding, no action needed.

---

Generated by Claude Code

[PatrickRose]

Re-checked after today's rebase (new head 90b0650, package-lock refresh only — same target version 7.0.2): typescript-eslint@latest is now 8.66.0 but its peer range is still >=4.8.4 <6.1.0, so the block from the previous diagnosis (#1044 (comment)) still applies. Holding, no action needed.

---

Generated by Claude Code

[PatrickRose]

Re-checked after today's rebase (new head fd85df5, package-lock refresh only — same target version 7.0.2): typescript-eslint@latest is still 8.66.0 with peer range >=4.8.4 <6.1.0, so the block from the previous diagnosis (#1044 (comment)) still applies. Holding, no action needed.

---

Generated by Claude Code

[PatrickRose]

Re-checked after today's rebase (new head 4cb8bb3, package-lock refresh only — same target version 7.0.2): typescript-eslint@latest is still 8.66.0 with peer range >=4.8.4 <6.1.0, so the block from the previous diagnosis (#1044 (comment)) still applies. Holding, no action needed.

---

Generated by Claude Code

[PatrickRose]

Re-checked after today's rebase (new head b9e44fc, package-lock refresh only — same target version 7.0.2): typescript-eslint@latest is still 8.66.0 with peer range >=4.8.4 <6.1.0, so the block from the original diagnosis (#1044 (comment)) still applies. Holding, no action needed.

---

Generated by Claude Code