Update dependency typescript to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	^5.9.3 → ^6.0.0

---

Release Notes

microsoft/TypeScript (typescript)

v6.0.2

Compare Source

---

Configuration

📅 Schedule: Branch creation - "after 7am every weekday,before 7pm every weekday" in timezone CET, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, 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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ 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: bun.lock

Command failed: bun install --ignore-scripts
Resolving dependencies
Resolved, downloaded and extracted [1]
error: GET https://repox.jfrog.io/artifactory/api/npm/npm/typescript - 401
error: typescript@^6.0.0 failed to resolve

[hashicorp-vault-sonar-prod]

Renovate Jira issue ID: CLI-261

[sonar-review-alpha]

Summary

This PR updates TypeScript from v5.9.3 to v6.0.0 (resolves to 6.0.2 in bun.lock). However, there is a critical compatibility issue: the pinned version of typescript-eslint@8.56.1 has a peer dependency constraint of "typescript": ">=4.8.4 <6.0.0", which explicitly excludes TypeScript 6.x. This mismatch will likely cause peer dependency warnings/errors and needs to be resolved before merging.

What reviewers should know

Before reviewing code changes:

• Check if the build/lint actually passes with this combination. The peer dependency conflict may prevent the project from building or running linters.
• If this PR was auto-generated by Renovate, it may be incomplete—typescript-eslint would typically need to be updated as well to support TypeScript 6.x.

Key points for reviewers:

• The changes are minimal: only package.json and bun.lock were modified
• The actual TypeScript package resolves to 6.0.2 in the lock file
• The typescript-eslint peer dependency mismatch is the blocker (check: does build succeed? do linters run?)
• Verify that dependencies don't need concurrent updates for TypeScript 6 compatibility

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[sonar-review-alpha]

Conclusion: This PR has a real compatibility problem that blocks merge — typescript-eslint@8.56.1 explicitly declares "typescript": ">=4.8.4 <6.0.0" as a peer dependency (visible in the lock file), meaning it does not support TypeScript 6.x. typescript-eslint needs to be bumped to a version that supports TS 6 before this can land safely.

🗣️ Give feedback

[sonar-review-alpha]

Incompatible peer dependency: typescript-eslint@8.56.1 declares "typescript": ">=4.8.4 <6.0.0" — it explicitly does not support TypeScript 6.x. Installing TypeScript 6.0.2 alongside this version creates a peer dependency conflict.

Linting (ESLint with @typescript-eslint/parser) may silently produce incorrect results, error out, or fail entirely. Check the typescript-eslint changelog and bump it alongside this TypeScript upgrade — typescript-eslint v8.x added TypeScript 6 support in a later minor release.

• Mark as noise