Skip to content

[RFR] ⬆️ #5: Upgrade dependency typescript to v5.8.3 #79

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 9, 2024

This PR contains the following updates:

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

Release Notes

microsoft/TypeScript (typescript)

v5.8.3

Compare Source

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:

v5.6.3: TypeScript 5.6.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.6.2: TypeScript 5.6

Compare Source

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

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

Copy link
Contributor Author

renovate bot commented Sep 9, 2024

⚠️ 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/build-angular@18.2.12
npm error Found: typescript@5.8.3
npm error node_modules/typescript
npm error   dev typescript@"5.8.3" from the root project
npm error   peerOptional typescript@">=4.9.5" from cosmiconfig@9.0.0
npm error   node_modules/cosmiconfig
npm error     cosmiconfig@"^9.0.0" from postcss-loader@8.1.1
npm error     node_modules/postcss-loader
npm error       postcss-loader@"8.1.1" from @angular-devkit/build-angular@18.2.12
npm error       node_modules/@angular-devkit/build-angular
npm error         dev @angular-devkit/build-angular@"18.2.12" from the root project
npm error   2 more (prettier-plugin-organize-imports, ts-api-utils)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=5.4 <5.6" from @angular-devkit/build-angular@18.2.12
npm error node_modules/@angular-devkit/build-angular
npm error   dev @angular-devkit/build-angular@"18.2.12" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.5.4
npm error node_modules/typescript
npm error   peer typescript@">=5.4 <5.6" from @angular-devkit/build-angular@18.2.12
npm error   node_modules/@angular-devkit/build-angular
npm error     dev @angular-devkit/build-angular@"18.2.12" 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/2025-04-05T02_43_15_615Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-04-05T02_43_15_615Z-debug-0.log

@renovate renovate bot force-pushed the renovate/typescript-5.x branch from 7413475 to 1c31ce3 Compare October 9, 2024 00:41
@renovate renovate bot changed the title [RFR] ⬆️ #5: Upgrade dependency typescript to v5.6.2 [RFR] ⬆️ #5: Upgrade dependency typescript to v5.6.3 Oct 9, 2024
Copy link

sonarqubecloud bot commented Oct 9, 2024

@renovate renovate bot force-pushed the renovate/typescript-5.x branch from 1c31ce3 to fcf1887 Compare November 22, 2024 20:47
@renovate renovate bot changed the title [RFR] ⬆️ #5: Upgrade dependency typescript to v5.6.3 [RFR] ⬆️ #5: Upgrade dependency typescript to v5.7.2 Nov 22, 2024
Copy link

@renovate renovate bot force-pushed the renovate/typescript-5.x branch from fcf1887 to cb61097 Compare January 8, 2025 23:08
@renovate renovate bot changed the title [RFR] ⬆️ #5: Upgrade dependency typescript to v5.7.2 [RFR] ⬆️ #5: Upgrade dependency typescript to v5.7.3 Jan 8, 2025
Copy link

sonarqubecloud bot commented Jan 8, 2025

@renovate renovate bot force-pushed the renovate/typescript-5.x branch from cb61097 to f36c75f Compare February 28, 2025 19:31
@renovate renovate bot changed the title [RFR] ⬆️ #5: Upgrade dependency typescript to v5.7.3 [RFR] ⬆️ #5: Upgrade dependency typescript to v5.8.2 Feb 28, 2025
Copy link

@renovate renovate bot force-pushed the renovate/typescript-5.x branch from f36c75f to 1e9f816 Compare April 5, 2025 02:43
@renovate renovate bot changed the title [RFR] ⬆️ #5: Upgrade dependency typescript to v5.8.2 [RFR] ⬆️ #5: Upgrade dependency typescript to v5.8.3 Apr 5, 2025
Copy link

sonarqubecloud bot commented Apr 5, 2025

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.

0 participants