Skip to content

chore(deps): update dependency typescript to v6#227

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/typescript-6.x
Open

chore(deps): update dependency typescript to v6#227
renovate[bot] wants to merge 1 commit intomainfrom
renovate/typescript-6.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 26, 2026

This PR contains the following updates:

Package Change Age Confidence
typescript (source) ^5.9.2^6.0.0 age confidence

Release Notes

microsoft/TypeScript (typescript)

v6.0.2

Compare Source


Configuration

📅 Schedule: 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 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

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

@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Mar 26, 2026

⚠️ 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: typia@12.0.1
npm error Found: typescript@6.0.2
npm error node_modules/typescript
npm error   dev typescript@"^6.0.0" from the root project
npm error   peerOptional typescript@">=4.9.5" from cosmiconfig@8.3.6
npm error   node_modules/cosmiconfig
npm error     cosmiconfig@"^8.2.0" from fork-ts-checker-webpack-plugin@9.1.0
npm error     node_modules/fork-ts-checker-webpack-plugin
npm error       dev fork-ts-checker-webpack-plugin@"^9.0.2" from the root project
npm error   1 more (fork-ts-checker-webpack-plugin)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=4.8.0 <5.10.0" from typia@12.0.1
npm error node_modules/typia
npm error   dev typia@"^12.0.1" from the root project
npm error   peer typia@"^12.0.1" from @typia/unplugin@12.0.1
npm error   node_modules/@typia/unplugin
npm error     dev @typia/unplugin@"^12.0.1" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peer typescript@">=4.8.0 <5.10.0" from typia@12.0.1
npm error   node_modules/typia
npm error     dev typia@"^12.0.1" from the root project
npm error     peer typia@"^12.0.1" from @typia/unplugin@12.0.1
npm error     node_modules/@typia/unplugin
npm error       dev @typia/unplugin@"^12.0.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 /runner/cache/others/npm/_logs/2026-04-01T19_25_21_512Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-01T19_25_21_512Z-debug-0.log

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages bot commented Mar 26, 2026

Deploying interview-proofreader with  Cloudflare Pages  Cloudflare Pages

Latest commit: 48acc7b
Status:🚫  Build failed.

View logs

@renovate renovate bot force-pushed the renovate/typescript-6.x branch from 388fcd8 to 48acc7b Compare April 1, 2026 19:25
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.

0 participants