[Codependence] update dependencies

[yowainwright]

Dependency updates

Auto-generated by [codependence][1] using [create-pull-request][2]
[1]: https://github.com/yowainwright/build-lambda-layer
[2]: https://github.com/peter-evans/create-pull-request

[greptile-apps]

Greptile Summary

This is an auto-generated dependency update PR that bumps typescript from 5.9.3 to 6.0.2 (a major version upgrade) and @typescript-eslint/eslint-plugin / @typescript-eslint/parser from 8.57.1 to 8.57.2 (patch). The lock file is updated accordingly.

Key concerns:

• The @typescript-eslint/*@8.57.2 packages (eslint-plugin, parser, project-service, tsconfig-utils, typescript-estree, type-utils, and related) all declare a peer dependency of typescript: '>=4.8.4 <6.0.0'. TypeScript 6.0.2 falls outside this range, causing a peer dependency violation that pnpm will warn about at install time and that may cause ESLint type-aware linting rules to malfunction.
• typescript-eslint@7.18.0 (the meta-package resolved via ^7.7.1) and tsutils@3.21.0 share similar TypeScript version constraints and are also affected.
• This upgrade should be accompanied by updating the @typescript-eslint suite to a version that explicitly supports TypeScript 6.x (or typescript-eslint v8+ meta-package), or TypeScript should be held at the latest 5.x release until the linting ecosystem is ready.

Confidence Score: 3/5

Merging risks silently breaking the linting toolchain due to a TypeScript 6.x peer dependency mismatch with the entire @typescript-eslint suite.

The TypeScript major-version bump to 6.0.2 conflicts with the explicitly declared typescript: '>=4.8.4 <6.0.0' peer dependency constraints across multiple @typescript-eslint packages. This is a present compatibility defect that could break lint CI steps and ESLint type-aware rules, not just a hypothetical risk.

package.json — the typescript version and @typescript-eslint / typescript-eslint versions need to be co-updated for compatibility.

Important Files Changed

Filename	Overview
package.json	TypeScript bumped from 5.9.3 to 6.0.2 (major version) and @typescript-eslint packages patched to 8.57.2; however, all @typescript-eslint 8.57.x packages declare typescript: '>=4.8.4 <6.0.0' as a peer dependency, so TS 6.0.2 is out-of-range and the linting toolchain may break.
pnpm-lock.yaml	Lock file updated to reflect typescript@6.0.2 across all peer-dependency slots; resolution metadata for @typescript-eslint/* packages clearly shows typescript: '>=4.8.4 <6.0.0' constraints, confirming the peer-dep violation introduced by the TypeScript major-version bump.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    TS["typescript@6.0.2\n(this PR)"]
    TSE_PLUGIN["@typescript-eslint/eslint-plugin@8.57.2\npeerDep: typescript >=4.8.4 <6.0.0"]
    TSE_PARSER["@typescript-eslint/parser@8.57.2\npeerDep: typescript >=4.8.4 <6.0.0"]
    TSE_ESTREE["@typescript-eslint/typescript-estree@8.57.2\npeerDep: typescript >=4.8.4 <6.0.0"]
    TSE_META["typescript-eslint@7.18.0\n(meta-package, ^7.7.1)"]
    TSUTILS["tsutils@3.21.0\n(legacy)"]
    LINT["pnpm lint\n(ESLint + type-aware rules)"]
    BUILD["pnpm build / typecheck\n(tsc / tsup)"]

    TS -->|"✅ major version, likely compatible"| BUILD
    TS -->|"❌ violates <6.0.0 constraint"| TSE_PLUGIN
    TS -->|"❌ violates <6.0.0 constraint"| TSE_PARSER
    TS -->|"❌ violates <6.0.0 constraint"| TSE_ESTREE
    TS -->|"⚠️ likely constraint violation"| TSE_META
    TS -->|"⚠️ old package, unsupported"| TSUTILS
    TSE_PLUGIN --> LINT
    TSE_PARSER --> LINT
    TSE_ESTREE --> LINT
    TSE_META --> LINT

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: package.json
Line: 69-70

Comment:
**TypeScript 6.x violates `@typescript-eslint` peer dependency constraints**

The `@typescript-eslint/eslint-plugin@8.57.2`, `@typescript-eslint/parser@8.57.2`, and related packages (`@typescript-eslint/project-service`, `@typescript-eslint/tsconfig-utils`, `@typescript-eslint/typescript-estree`, `@typescript-eslint/type-utils`) all declare a peer dependency of `typescript: '>=4.8.4 <6.0.0'` (visible in `pnpm-lock.yaml`). TypeScript 6.0.2 is outside this supported range.

Similarly, `typescript-eslint@^7.7.1` (resolved to `7.18.0`) and `tsutils@^3.21.0` also have similar constraints.

This peer dependency mismatch means:
- pnpm will emit unsatisfied peer dependency warnings at install time
- ESLint's type-aware linting rules may produce incorrect results or fail outright, since the `@typescript-eslint` AST parser is not guaranteed to work with TypeScript 6.x's compiler API
- The `typecheck` and `lint` CI steps are at risk of producing false negatives

To resolve this, the `@typescript-eslint` packages should be upgraded to a version that explicitly supports TypeScript 6.x (likely `@typescript-eslint/*` v8.58+ or the `typescript-eslint` v8 meta-package), or TypeScript should remain at the latest 5.x release until the linting toolchain catches up.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "Update dependencies" | Re-trigger Greptile}

[greptile-apps]

TypeScript 6.x violates @typescript-eslint peer dependency constraints

The @typescript-eslint/eslint-plugin@8.57.2, @typescript-eslint/parser@8.57.2, and related packages (@typescript-eslint/project-service, @typescript-eslint/tsconfig-utils, @typescript-eslint/typescript-estree, @typescript-eslint/type-utils) all declare a peer dependency of typescript: '>=4.8.4 <6.0.0' (visible in pnpm-lock.yaml). TypeScript 6.0.2 is outside this supported range.

Similarly, typescript-eslint@^7.7.1 (resolved to 7.18.0) and tsutils@^3.21.0 also have similar constraints.

This peer dependency mismatch means:

• pnpm will emit unsatisfied peer dependency warnings at install time
• ESLint's type-aware linting rules may produce incorrect results or fail outright, since the @typescript-eslint AST parser is not guaranteed to work with TypeScript 6.x's compiler API
• The typecheck and lint CI steps are at risk of producing false negatives

To resolve this, the @typescript-eslint packages should be upgraded to a version that explicitly supports TypeScript 6.x (likely @typescript-eslint/* v8.58+ or the typescript-eslint v8 meta-package), or TypeScript should remain at the latest 5.x release until the linting toolchain catches up.

Prompt To Fix With AI

This is a comment left during a code review.
Path: package.json
Line: 69-70

Comment:
**TypeScript 6.x violates `@typescript-eslint` peer dependency constraints**

The `@typescript-eslint/eslint-plugin@8.57.2`, `@typescript-eslint/parser@8.57.2`, and related packages (`@typescript-eslint/project-service`, `@typescript-eslint/tsconfig-utils`, `@typescript-eslint/typescript-estree`, `@typescript-eslint/type-utils`) all declare a peer dependency of `typescript: '>=4.8.4 <6.0.0'` (visible in `pnpm-lock.yaml`). TypeScript 6.0.2 is outside this supported range.

Similarly, `typescript-eslint@^7.7.1` (resolved to `7.18.0`) and `tsutils@^3.21.0` also have similar constraints.

This peer dependency mismatch means:
- pnpm will emit unsatisfied peer dependency warnings at install time
- ESLint's type-aware linting rules may produce incorrect results or fail outright, since the `@typescript-eslint` AST parser is not guaranteed to work with TypeScript 6.x's compiler API
- The `typecheck` and `lint` CI steps are at risk of producing false negatives

To resolve this, the `@typescript-eslint` packages should be upgraded to a version that explicitly supports TypeScript 6.x (likely `@typescript-eslint/*` v8.58+ or the `typescript-eslint` v8 meta-package), or TypeScript should remain at the latest 5.x release until the linting toolchain catches up.

How can I resolve this? If you propose a fix, please make it concise.