Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 28, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
typescript (source) 5.6.3 -> 5.8.2 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

microsoft/TypeScript (typescript)

v5.8.2

Compare Source

v5.7.3: TypeScript 5.7.3

Compare Source

For release notes, check out the release announcement.

Downloads are available on npm

v5.7.2: TypeScript 5.7

Compare Source

For release notes, check out the release announcement.

Downloads are available on:


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 renovate bot added the renovatebot label Feb 28, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Feb 28, 2025

⚠️ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: typia@7.6.4
npm ERR! Found: typescript@5.8.2
npm ERR! node_modules/typescript
npm ERR!   typescript@"5.8.2" from the root project
npm ERR!   peer typescript@"*" from @deepkit/type-compiler@1.0.2
npm ERR!   node_modules/@deepkit/type-compiler
npm ERR!     @deepkit/type-compiler@"1.0.2" from the root project
npm ERR!   7 more (compatfactory, gts, ts-json-validator, ts-node, tsutils, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@">=4.8.0 <5.8.0" from typia@7.6.4
npm ERR! node_modules/typia
npm ERR!   typia@"7.6.4" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: typescript@5.7.3
npm ERR! node_modules/typescript
npm ERR!   peer typescript@">=4.8.0 <5.8.0" from typia@7.6.4
npm ERR!   node_modules/typia
npm ERR!     typia@"7.6.4" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-03-02T17_49_11_005Z-debug-0.log

@renovate renovate bot force-pushed the renovate/typescript-5.x branch 10 times, most recently from 8a87a51 to 58af1eb Compare March 2, 2025 13:31
@renovate renovate bot force-pushed the renovate/typescript-5.x branch from 58af1eb to 25f1e16 Compare March 2, 2025 17:49
@DarkGL DarkGL closed this Mar 3, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Mar 3, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (5.8.2). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

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

@renovate renovate bot deleted the renovate/typescript-5.x branch March 3, 2025 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants