Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Jul 11, 2022

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
typescript (source) ~4.6.1~4.9.0 age confidence

Release Notes

microsoft/TypeScript (typescript)

v4.9.5: TypeScript 4.9.5

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

Changes:

v4.9.4: TypeScript 4.9.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

Changes:

This list of changes was auto generated.

v4.9.3: TypeScript 4.9

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

Changes:

See More

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.

@vercel
Copy link

vercel bot commented Jul 11, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
accordion-simple ❌ Failed (Inspect) Apr 4, 2023 9:54am

@renovate renovate bot force-pushed the renovate/typescript-4.x branch from 6e21371 to aad221f Compare July 19, 2022 14:53
@renovate renovate bot force-pushed the renovate/typescript-4.x branch from aad221f to d50009f Compare August 26, 2022 00:49
@renovate renovate bot changed the title chore(deps): update dependency typescript to v4.7.4 chore(deps): update dependency typescript to v4.8.2 Aug 26, 2022
@renovate renovate bot force-pushed the renovate/typescript-4.x branch from d50009f to c5b77c9 Compare September 8, 2022 18:37
@renovate renovate bot changed the title chore(deps): update dependency typescript to v4.8.2 chore(deps): update dependency typescript to v4.8.3 Sep 8, 2022
@renovate renovate bot force-pushed the renovate/typescript-4.x branch from c5b77c9 to 89c3f66 Compare November 8, 2022 13:38
@renovate renovate bot changed the title chore(deps): update dependency typescript to v4.8.3 chore(deps): update dependency typescript to ~4.8.0 Nov 8, 2022
@renovate renovate bot force-pushed the renovate/typescript-4.x branch from 89c3f66 to b003403 Compare November 15, 2022 21:56
@renovate renovate bot changed the title chore(deps): update dependency typescript to ~4.8.0 chore(deps): update dependency typescript to ~4.9.0 Nov 15, 2022
@renovate
Copy link
Author

renovate bot commented Nov 15, 2022

⚠ 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: @angular-devkit/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"~4.9.0" from the root project
npm ERR!   peer typescript@"*" from @angular-eslint/[email protected]
npm ERR!   node_modules/@angular-eslint/builder
npm ERR!     dev @angular-eslint/builder@"^14.1.2" from the root project
npm ERR!   9 more (@angular-eslint/eslint-plugin, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@">=4.6.2 <4.9" from @angular-devkit/[email protected]
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   dev @angular-devkit/build-angular@"^14.2.8" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/typescript
npm ERR!   peer typescript@">=4.6.2 <4.9" from @angular-devkit/[email protected]
npm ERR!   node_modules/@angular-devkit/build-angular
npm ERR!     dev @angular-devkit/build-angular@"^14.2.8" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2022-11-15T21_56_33_897Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-11-15T21_56_33_897Z-debug-0.log

@renovate renovate bot changed the title chore(deps): update dependency typescript to ~4.9.0 Update dependency typescript to ~4.9.0 Dec 17, 2022
@renovate renovate bot changed the title Update dependency typescript to ~4.9.0 chore(deps): update dependency typescript to ~4.9.0 Dec 17, 2022
@renovate renovate bot changed the title chore(deps): update dependency typescript to ~4.9.0 chore(deps): update dependency typescript to ~4.9.0 - autoclosed Apr 3, 2023
@renovate renovate bot closed this Apr 3, 2023
@renovate renovate bot deleted the renovate/typescript-4.x branch April 3, 2023 23:25
@renovate renovate bot changed the title chore(deps): update dependency typescript to ~4.9.0 - autoclosed chore(deps): update dependency typescript to ~4.9.0 Apr 4, 2023
@renovate renovate bot reopened this Apr 4, 2023
@renovate renovate bot restored the renovate/typescript-4.x branch April 4, 2023 09:52
@renovate
Copy link
Author

renovate bot commented Aug 10, 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @angular-devkit/[email protected]
npm error Found: [email protected]
npm error node_modules/typescript
npm error   dev typescript@"~4.9.0" from the root project
npm error   peer typescript@"*" from @angular-eslint/[email protected]
npm error   node_modules/@angular-eslint/builder
npm error     dev @angular-eslint/builder@"^14.1.2" from the root project
npm error   9 more (@angular-eslint/eslint-plugin, ...)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=4.6.2 <4.9" from @angular-devkit/[email protected]
npm error node_modules/@angular-devkit/build-angular
npm error   dev @angular-devkit/build-angular@"^14.2.8" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/typescript
npm error   peer typescript@">=4.6.2 <4.9" from @angular-devkit/[email protected]
npm error   node_modules/@angular-devkit/build-angular
npm error     dev @angular-devkit/build-angular@"^14.2.8" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error 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-01-08T18_12_58_846Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-01-08T18_12_58_846Z-debug-0.log

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