chore(deps-dev): bump typescript from 5.9.3 to 6.0.3 in /app#602
chore(deps-dev): bump typescript from 5.9.3 to 6.0.3 in /app#602dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [typescript](https://github.com/microsoft/TypeScript) from 5.9.3 to 6.0.3. - [Release notes](https://github.com/microsoft/TypeScript/releases) - [Commits](microsoft/TypeScript@v5.9.3...v6.0.3) --- updated-dependencies: - dependency-name: typescript dependency-version: 6.0.3 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Completed Working on "Code Review"✅ Review publishing complete. Posted comments from all chunks and submitted final review: COMMENT. Total comments: 2 across 1 files. ✅ Workflow completed successfully. |
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files
|
There was a problem hiding this comment.
Summary of posted review findings:
- 2 MAJOR issues identified (0 BLOCKER, 0 CRITICAL, 0 MINOR, 0 SUGGESTION, 0 PRAISE)
- Affected file(s):
app/package-lock.json
Key themes:
- Dependency compatibility risk: TypeScript was upgraded to 6.0.3 while resolved
@typescript-eslintpeer ranges still indicate<6.0.0, creating an unsupported lint/tooling combination. - Lockfile reproducibility drift across Linux environments: removal of explicit
libcselectors on optional native packages may reduce deterministic binary resolution between glibc and musl systems.
Recommended next steps:
- Upgrade the
typescript-eslintstack to versions that explicitly support TypeScript 6 (or keep TypeScript below 6 until that is done), then regenerate the lockfile. - Regenerate
package-lock.jsonwith pinned npm/toolchain versions and validate clean installs in both glibc and musl environments to confirm reproducible native package resolution.
| "peerDependencies": { | ||
| "@typescript-eslint/parser": "^8.57.2", | ||
| "eslint": "^8.57.0 || ^9.0.0 || ^10.0.0", | ||
| "typescript": ">=4.8.4 <6.0.0" |
There was a problem hiding this comment.
[major]: Multiple findings report the same issue: lockfile installs TypeScript 6.0.3 while resolved @typescript-eslint packages still require peer "typescript": ">=4.8.4 <6.0.0" (including nested relocation under typescript-eslint). This is an unsupported toolchain combination that can cause lint/parser instability and CI failures.
Upgrade the typescript-eslint stack (and related @typescript-eslint packages) to versions that explicitly support TypeScript 6, or keep TypeScript below 6 until that upgrade; then regenerate package-lock.json so peer ranges align.
| "arm64" | ||
| ], | ||
| "dev": true, | ||
| "libc": [ |
There was a problem hiding this comment.
[major]: Lockfile changes remove explicit libc constraints from optional native package entries (glibc vs musl), which can make binary resolution less reproducible between environments (e.g., CI vs Alpine runtime) and increase risk of native binary mismatch.
Regenerate lockfile with a pinned npm/toolchain version that preserves stable libc-aware metadata (or otherwise enforce deterministic install tooling), and validate clean installs on both glibc and musl environments.
Bumps typescript from 5.9.3 to 6.0.3.
Release notes
Sourced from typescript's releases.
Commits
050880cBump version to 6.0.3 and LKGeeae9dd🤖 Pick PR #63401 (Also check package name validity in...) into release-6.0 (#...ad1c695🤖 Pick PR #63368 (Harden ATA package name filtering) into release-6.0 (#63372)0725fb4🤖 Pick PR #63310 (Mark class property initializers as...) into release-6.0 (#...607a22aBump version to 6.0.2 and LKG9e72ab7🤖 Pick PR #63239 (Fix missing lib files in reused pro...) into release-6.0 (#...35ff23d🤖 Pick PR #63163 (Port anyFunctionType subtype fix an...) into release-6.0 (#...e175b69Bump version to 6.0.1-rc and LKGaf4caacUpdate LKG8efd7e8Merge remote-tracking branch 'origin/main' into release-6.0Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)