chore(deps): update dependency typescript to v6

[renovate]

This PR contains the following updates:

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

---

Release Notes

microsoft/TypeScript (typescript)

v6.0.3

Compare Source

v6.0.2

Compare Source

---

Configuration

📅 Schedule: (in timezone Europe/London)

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

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

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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: 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: @kitajs/ts-html-plugin@4.1.4
npm error Found: typescript@6.0.3
npm error node_modules/typescript
npm error   dev typescript@"^6.0.3" from the root project
npm error   peer typescript@">= 4.3" from @swc-node/register@1.11.1
npm error   node_modules/@swc-node/register
npm error     dev @swc-node/register@"^1.11.1" from the root project
npm error   10 more (@typescript-eslint/eslint-plugin, ...)
npm error
npm error Could not resolve dependency:
npm error peer typescript@"^5.9.3" from @kitajs/ts-html-plugin@4.1.4
npm error node_modules/@kitajs/ts-html-plugin
npm error   @kitajs/ts-html-plugin@"^4.1.4" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peer typescript@"^5.9.3" from @kitajs/ts-html-plugin@4.1.4
npm error   node_modules/@kitajs/ts-html-plugin
npm error     @kitajs/ts-html-plugin@"^4.1.4" 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 /runner/cache/others/npm/_logs/2026-04-20T01_47_26_234Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-20T01_47_26_234Z-debug-0.log

[Copilot]

Pull request overview

This PR upgrades the repo’s TypeScript toolchain dependency to the v6 line (and updates the lockfile accordingly), which impacts compilation/typechecking and tooling that consumes the TypeScript compiler API.

Changes:

• Bump typescript devDependency from ^5.9.3 to ^6.0.3
• Update package-lock.json to reflect the new dependency graph
• Bump package version 0.9.84 → 0.9.85

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
package.json	Updates project version and TypeScript devDependency.
package-lock.json	Locks TypeScript 6.0.3 and updates resolved dependency tree (including a nested TypeScript for @tsoa/cli).

[Copilot]

The PR updates TypeScript, but it also bumps the package version (0.9.84 → 0.9.85). This isn't mentioned in the PR description and affects the CLI/version endpoints that read from package.json; consider either documenting the version bump in the PR description or splitting it into a separate release/versioning change.

[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.