fix: bump typescript from 5.9.3 to 6.0.3 - #272
Merged
Merged
Conversation
Bumps [typescript](https://github.com/microsoft/TypeScript) from 5.9.3 to 7.0.2. - [Release notes](https://github.com/microsoft/TypeScript/releases) - [Commits](https://github.com/microsoft/TypeScript/commits) --- updated-dependencies: - dependency-name: typescript dependency-version: 7.0.2 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Contributor
Author
|
Dependabot can't resolve your JavaScript dependency files. Because of this, Dependabot cannot update this pull request. |
dannyneira
approved these changes
Aug 3, 2026
Contributor
Author
|
Dependabot can't resolve your JavaScript dependency files. Because of this, Dependabot cannot update this pull request. |
Resolve merge conflicts in package.json and package-lock.json by taking main as baseline and setting typescript to ^6.0.0 (resolves to 6.0.3). TypeScript 7.0.2 (the original dependabot proposal) is incompatible with the repo's pinned peer dependencies: - @typescript-eslint/parser@8.65.0 peer: typescript >=4.8.4 <6.1.0 - ts-jest@29.4.11 peer: typescript >=4.3 <7 6.0.3 is the latest 6.x stable and the maximum safe upgrade within all peer constraints. Lockfile regenerated via npm install --legacy-peer-deps + npm audit fix: - typescript: 5.9.3 -> 6.0.3 - brace-expansion: 5.0.8 -> 5.0.9 (remediates GHSA-rgw5-rvv9-x895 / CVE-2026-69152, Dependabot alert #76) - npm audit: 0 vulnerabilities dist/ rebuilt with TypeScript 6.0.3 (ncc build). Note: ESLint lint step fails due to a pre-existing main issue (@stylistic/eslint-plugin@5.10.0 rule naming incompatibility with eslint@10.8.0), unrelated to this TypeScript bump. Co-Authored-By: Warp Agent <agent@warp.dev>
dannyneira
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps
typescriptfrom 5.9.3 to 6.0.3 (latest 6.x stable) and mergesorigin/mainto resolve conflicts.Why not TypeScript 7.0.2?
TypeScript 7.0.2 violates two install-blocking peer dependency constraints:
@typescript-eslint/parser@8.65.0typescript >=4.8.4 <6.1.0ts-jest@29.4.11typescript >=4.3 <7No published
typescript-eslintrelease supports TypeScript 7 yet (latest8.66.0still caps at<6.1.0). TS 7 is blocked on upstream support.Changes
package.json:typescript: "^5.0.0"→"^6.0.0"(resolves to 6.0.3)package-lock.json: regenerated vianpm install --legacy-peer-deps+npm audit fixtypescript: 5.9.3 → 6.0.3brace-expansion: 5.0.8 → 5.0.9 — remediates GHSA-rgw5-rvv9-x895 / CVE-2026-69152 (Dependabot alert Bump @types/node from 16.10.5 to 18.7.19 #76)npm audit: 0 vulnerabilitiesdist/: rebuilt with TypeScript 6.0.3 (ncc build)Validation
tsc(build)prettier --check(format-check)ncc build(package)check-distequivalent (git diff dist/after rebuild)npm auditeslint(lint)ESLint note
The
npm run lintstep fails due to a pre-existing issue onmainunrelated to this TypeScript bump:@stylistic/eslint-plugin@5.10.0rule naming incompatibility witheslint@10.8.0(
Could not find "func-call-spacing" in plugin "@stylistic").This was introduced by PRs #271 (eslint 9→10) and #278 (@Stylistic 2.13→5.10) and
also causes
npm installto ERESOLVE-fail on main (eslint-plugin-import@2.32.0does not support eslint 10). Both issues exist on
mainindependent of this PR.Merge info
origin/main(63719a8) into the branch viagit merge --no-ff(no rebase/force-push)package.jsonandpackage-lock.json,then setting
typescript: "^6.0.0"and regenerating the lockfile via npmCo-Authored-By: Warp Agent agent@warp.dev