Skip to content

Update dependency typescript to v7#2261

Closed
red-hat-konflux[bot] wants to merge 1 commit into
pattern-fly-5from
konflux/mintmaker/pattern-fly-5/typescript-7.x
Closed

Update dependency typescript to v7#2261
red-hat-konflux[bot] wants to merge 1 commit into
pattern-fly-5from
konflux/mintmaker/pattern-fly-5/typescript-7.x

Conversation

@red-hat-konflux

@red-hat-konflux red-hat-konflux Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
typescript (source) ^5.9.3^7.0.0 age confidence

Release Notes

microsoft/TypeScript (typescript)

v7.0.2

Compare Source

v6.0.3: TypeScript 6.0.3

Compare Source

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

Downloads are available on:

v6.0.2: TypeScript 6.0

Compare Source

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

Downloads are available on:


Configuration

📅 Schedule: (in timezone UTC)

  • Branch creation
    • Every minute (* * * * *)
  • Automerge
    • At any time (no schedule defined)

🚦 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 this update again.


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

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux

Copy link
Copy Markdown
Contributor Author

⚠️ 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: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/eslint-plugin@8.59.0
npm error Found: typescript@7.0.2
npm error node_modules/typescript
npm error   typescript@"^7.0.0" from the root project
npm error   peer typescript@">=4.5.5" from @openshift-console/dynamic-plugin-sdk-webpack@1.1.1
npm error   node_modules/@openshift-console/dynamic-plugin-sdk-webpack
npm error     @openshift-console/dynamic-plugin-sdk-webpack@"1.1.1" from the root project
npm error   4 more (cosmiconfig, ts-api-utils, ts-loader, ts-node)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/eslint-plugin@8.59.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"^8.58.1" from the root project
npm error
npm error Conflicting peer dependency: typescript@6.0.3
npm error node_modules/typescript
npm error   peer typescript@">=4.8.4 <6.1.0" from @typescript-eslint/eslint-plugin@8.59.0
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"^8.58.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-07-22T18_15_27_759Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-07-22T18_15_27_759Z-debug-0.log

@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

Updates the typescript dependency constraint in package.json from ^5.9.3 to ^7.0.0.

Changes

TypeScript dependency upgrade

Layer / File(s) Summary
Update TypeScript dependency
package.json
Changes the typescript dependency constraint from ^5.9.3 to ^7.0.0.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Suggested labels: lgtm, approved

Suggested reviewers: kyoto, sriroopar

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: updating the TypeScript dependency to v7.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch konflux/mintmaker/pattern-fly-5/typescript-7.x

Comment @coderabbitai help to get the list of available commands.

@openshift-ci
openshift-ci Bot requested review from joshuawilson and syedriko July 22, 2026 18:17
@openshift-ci

openshift-ci Bot commented Jul 22, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign xrajesh for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 53: Update the TypeScript dependency in package.json from ^7.0.0 to a
version below 6.1.0, matching the existing package-lock.json and
`@typescript-eslint/parser` support range; keep the manifest and lockfile versions
aligned.
- Line 53: Revert the TypeScript dependency change in package.json from ^7.0.0
and retain a TypeScript 6-compatible package for tooling, using the project’s
dependency conventions or an npm alias if needed. Ensure the resolved TypeScript
version satisfies `@typescript-eslint/parser`’s <6.1.0 requirement while
preserving access to TypeScript 6.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: cf3858cd-9fe7-452c-89c8-c98724c5f456

📥 Commits

Reviewing files that changed from the base of the PR and between d9c2fbc and 6fcf9d0.

📒 Files selected for processing (1)
  • package.json

Comment thread package.json
"ts-loader": "^9.6.0",
"ts-node": "^10.9.2",
"typescript": "^5.9.3",
"typescript": "^7.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== package.json relevant lines ==\n'
nl -ba package.json | sed -n '45,60p'

printf '\n== package-lock.json TypeScript references ==\n'
rg -n '"typescript"|typescript@|typescript' package-lock.json | sed -n '1,80p'

printf '\n== package.json lint/tooling deps ==\n'
rg -n '"`@typescript-eslint/parser`"|@"typescript-eslint/parser"|typescript-eslint|eslint' package.json

printf '\n== package-lock.json `@typescript-eslint/parser` package entry ==\n'
rg -n '"`@typescript-eslint/parser`"|typescript' package-lock.json | sed -n '1,120p'

Repository: openshift/lightspeed-console

Length of output: 241


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== package.json relevant lines ==\n'
sed -n '45,60p' package.json

printf '\n== package-lock.json TypeScript references ==\n'
rg -n '"typescript"|typescript@|`@typescript-eslint/parser`' package-lock.json | sed -n '1,140p'

printf '\n== package.json lint/tooling deps ==\n'
rg -n '"`@typescript-eslint/parser`"|typescript-eslint|eslint|typescript' package.json

Repository: openshift/lightspeed-console

Length of output: 2277


Keep TypeScript within the parser’s supported range

package-lock.json is still pinned to typescript: ^5.9.3, and @typescript-eslint/parser in the current toolchain only supports typescript <6.1.0. Bumping the manifest to ^7.0.0 will leave installs/linting on an incompatible compiler. Update the TypeScript version together with the lint toolchain, or keep it below 6.1.0.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 53, Update the TypeScript dependency in package.json
from ^7.0.0 to a version below 6.1.0, matching the existing package-lock.json
and `@typescript-eslint/parser` support range; keep the manifest and lockfile
versions aligned.

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== package.json ==\n'
cat -n package.json | sed -n '1,220p'

printf '\n== lockfile candidates ==\n'
git ls-files | rg '(^|/)(package-lock\.json|pnpm-lock\.yaml|yarn\.lock|bun\.lockb|eslint.*config|tsconfig.*\.json)$' || true

printf '\n== typescript-eslint / typescript refs ==\n'
rg -n '"`@typescript-eslint/parser`"|"typescript"|typescript-eslint|parserOptions|eslint' package.json **/package.json **/pnpm-lock.yaml **/package-lock.json **/yarn.lock 2>/dev/null || true

Repository: openshift/lightspeed-console

Length of output: 5367


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Show focused manifests if present
for f in package.json pnpm-lock.yaml package-lock.json yarn.lock; do
  if [[ -f "$f" ]]; then
    printf '\n== %s ==\n' "$f"
    case "$f" in
      package.json) cat -n "$f" | sed -n '1,220p' ;;
      pnpm-lock.yaml) rg -n '^ *(`@typescript-eslint/parser`|typescript@|typescript-eslint)' "$f" | sed -n '1,120p' ;;
      package-lock.json) rg -n '"`@typescript-eslint/parser`"|"typescript"' "$f" | sed -n '1,120p' ;;
      yarn.lock) rg -n '^(`@typescript-eslint/parser`|typescript)@' "$f" | sed -n '1,120p' ;;
    esac
  fi
done

printf '\n== eslint config files ==\n'
git ls-files | rg '(^|/)(eslint\.config\.[cm]?[jt]s|\.eslintrc(\.[cm]?[jt]s|\.json|\.yml|\.yaml)?)$' || true

Repository: openshift/lightspeed-console

Length of output: 5217


🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== package.json ==\n'
cat -n package.json | sed -n '1,220p'

printf '\n== lockfile / config files ==\n'
git ls-files | rg '(^|/)(package-lock\.json|pnpm-lock\.yaml|yarn\.lock|bun\.lockb|eslint\.config\.[cm]?[jt]s|\.eslintrc(\.[cm]?[jt]s|\.json|\.yml|\.yaml)?)$' || true

printf '\n== type/lint references ==\n'
rg -n '"`@typescript-eslint/parser`"|"typescript"|"eslint"' package.json pnpm-lock.yaml package-lock.json yarn.lock .eslintrc* eslint.config.* 2>/dev/null || true

Repository: openshift/lightspeed-console

Length of output: 6461


🏁 Script executed:

#!/bin/bash
set -euo pipefail

python3 - <<'PY'
import json, os
from pathlib import Path

p = Path('package.json')
data = json.loads(p.read_text())
for section in ('dependencies', 'devDependencies', 'peerDependencies', 'optionalDependencies'):
    if section in data:
        print(f'== {section} ==')
        for k,v in data[section].items():
            if 'typescript' in k.lower() or 'eslint' in k.lower():
                print(f'{k}: {v}')
PY

printf '\n== lockfile facts ==\n'
for f in pnpm-lock.yaml package-lock.json yarn.lock; do
  if [[ -f "$f" ]]; then
    echo "-- $f --"
    rg -n '`@typescript-eslint/parser`|typescript@|typescript-eslint' "$f" | sed -n '1,80p'
  fi
done

printf '\n== eslint config references ==\n'
git ls-files | rg '(^|/)(eslint\.config\.[cm]?[jt]s|\.eslintrc(\.[cm]?[jt]s|\.json|\.yml|\.yaml)?)$' | sed -n '1,80p'

Repository: openshift/lightspeed-console

Length of output: 5249


🌐 Web query:

typescript-eslint TypeScript 7 support peer dependency range 2026

💡 Result:

As of July 22, 2026, typescript-eslint does not support TypeScript 7 [1][2]. The current peer dependency range for typescript-eslint is >=4.8.4 <6.1.0 [3][2], which explicitly excludes TypeScript 7.x [2]. Because TypeScript 7.0 does not ship with a programmatic API comparable to previous versions, typescript-eslint is currently unable to interface with it [1][4]. Official guidance from the TypeScript team and the typescript-eslint project recommends maintaining a side-by-side installation if you need both TypeScript 7 for compilation and TypeScript 6 for tooling like ESLint [1][4]. To work around this, you can use npm aliases to keep TypeScript 6 installed for your development tools while using TypeScript 7 for your project: 1. Install TypeScript 6 as an alias: npm install -D typescript@npm:@typescript/typescript6@^6.0.2 2. Use your package manager's configuration to ensure typescript-eslint resolves to the TypeScript 6 peer dependency [4]. Attempts to run typescript-eslint with TypeScript 7 will result in runtime exceptions because the tool relies on internal TypeScript APIs that have changed or are not exposed in the 7.0 release [1][5]. The project team is tracking this issue but has indicated that support cannot be added until an appropriate API is available [1].

Citations:


Do not bump typescript to 7 yet. @typescript-eslint/parser in package-lock.json still requires typescript >=4.8.4 <6.1.0, so ESLint will run against an unsupported compiler. Keep TypeScript 6 available for tooling (for example via an npm alias) until typescript-eslint supports TS7.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 53, Revert the TypeScript dependency change in
package.json from ^7.0.0 and retain a TypeScript 6-compatible package for
tooling, using the project’s dependency conventions or an npm alias if needed.
Ensure the resolved TypeScript version satisfies `@typescript-eslint/parser`’s
<6.1.0 requirement while preserving access to TypeScript 6.

@coderabbitai coderabbitai Bot mentioned this pull request Jul 22, 2026
1 task
@kyoto

kyoto commented Jul 23, 2026

Copy link
Copy Markdown
Member

Don't want to upgrade to TypeScript 7 yet

@kyoto kyoto closed this Jul 23, 2026
@kyoto
kyoto deleted the konflux/mintmaker/pattern-fly-5/typescript-7.x branch July 23, 2026 02:23
@red-hat-konflux

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 7.x releases. But if you manually upgrade to 7.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant