directory-connector
directory-connector copied to clipboard

Published 20 hours ago •

Reame
Issues

[deps]: Update typescript to v5

Open renovate[bot] opened this issue 1 year ago • 2 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
typescript (source)	`4.9.5` -> `5.5.4`

Release Notes

Microsoft/TypeScript (typescript)

`v5.5.4`

`v5.5.3`

`v5.5.2`

`v5.4.5`: TypeScript 5.4.5

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.4.4`: TypeScript 5.4.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.4.3`: TypeScript 5.4.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.4.2`: TypeScript 5.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.3.3`: TypeScript 5.3.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.3.2`: TypeScript 5.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.2.2`: TypeScript 5.2

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.1.6`: TypeScript 5.1.6

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on npm

`v5.1.5`: TypeScript 5.1.5

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v5.1.3`: TypeScript 5.1.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

NuGet package

`v5.0.4`: TypeScript 5.0.4

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v5.0.3`: TypeScript 5.0.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

`v5.0.2`: TypeScript 5.0

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

Configuration

📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (UTC), 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.

Aug 19 '24 01:08 renovate[bot]

⚠️ 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 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@"5.6.2" from the root project
npm error   peer typescript@"*" from @angular-eslint/[email protected]
npm error   node_modules/@angular-eslint/eslint-plugin-template
npm error     dev @angular-eslint/eslint-plugin-template@"17.2.0" from the root project
npm error   16 more (@angular-eslint/template-parser, ...)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=4.9.3 <5.2" from @angular-devkit/[email protected]
npm error node_modules/@angular-devkit/build-angular
npm error   peer @angular-devkit/build-angular@">=13.0.0 <17.0.0" from [email protected]
npm error   node_modules/jest-preset-angular
npm error     dev jest-preset-angular@"13.1.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/typescript
npm error   peer typescript@">=4.9.3 <5.2" from @angular-devkit/[email protected]
npm error   node_modules/@angular-devkit/build-angular
npm error     peer @angular-devkit/build-angular@">=13.0.0 <17.0.0" from [email protected]
npm error     node_modules/jest-preset-angular
npm error       dev jest-preset-angular@"13.1.1" 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 /tmp/renovate/cache/others/npm/_logs/2024-09-09T19_32_25_321Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-09T19_32_25_321Z-debug-0.log

Aug 19 '24 01:08 renovate[bot]

Internal tracking:

ID: AC-3002
Link: https://bitwarden.atlassian.net/browse/AC-3002

Aug 19 '24 01:08 bitwarden-bot

We have a conflict with Angular here and can not upgrade just yet

Sep 10 '24 15:09 addisonbeck

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

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

Sep 10 '24 15:09 renovate[bot]

@addisonbeck can we at least upgrade to [email protected], which looks like it would satisfy that dependency error? Just getting into v5 would be an improvement.

Sep 23 '24 00:09 eliykat