Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update dependency typescript to v5 #40

Closed
wants to merge 1 commit into from
Closed

Update dependency typescript to v5 #40

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 17, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

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

Release Notes

Microsoft/TypeScript (typescript)

v5.3.3: TypeScript 5.3.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.3.2: TypeScript 5.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.2.2: TypeScript 5.2

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.1.6: TypeScript 5.1.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 npm

v5.1.5: TypeScript 5.1.5

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.1.3: TypeScript 5.1.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.0.4: TypeScript 5.0.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:

v5.0.3: TypeScript 5.0.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.0.2: TypeScript 5.0

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 - "before 3am every weekday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Mar 17, 2023 •
edited
Loading

⚠ 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: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"5.3.3" from the root project
npm ERR!   peer typescript@">=4.2.0" from [email protected]
npm ERR!   node_modules/ts-api-utils
npm ERR!     ts-api-utils@"^1.0.1" from @typescript-eslint/[email protected]
npm ERR!     node_modules/@typescript-eslint/eslint-plugin
npm ERR!       dev @typescript-eslint/eslint-plugin@"^6.0.0" from the root project
npm ERR!     ts-api-utils@"^1.0.1" from @typescript-eslint/[email protected]
npm ERR!     node_modules/@typescript-eslint/type-utils
npm ERR!       @typescript-eslint/type-utils@"6.14.0" from @typescript-eslint/[email protected]
npm ERR!       node_modules/@typescript-eslint/eslint-plugin
npm ERR!         dev @typescript-eslint/eslint-plugin@"^6.0.0" from the root project
npm ERR!     1 more (@typescript-eslint/typescript-estree)
npm ERR!   1 more (ts-loader)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer typescript@">=3.8 <5.0" from [email protected]
npm ERR! node_modules/ts-jest
npm ERR!   dev ts-jest@"^27.1.3" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/typescript
npm ERR!   peer typescript@">=3.8 <5.0" from [email protected]
npm ERR!   node_modules/ts-jest
npm ERR!     dev ts-jest@"^27.1.3" 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 /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2023-12-18T04_55_32_401Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-typescript branch 2 times, most recently from 46b8ca7 to 9cab5d6 Compare April 4, 2023 16:51
@renovate renovate bot force-pushed the renovate/major-typescript branch from 9cab5d6 to f6c77b1 Compare April 7, 2023 19:55
@renovate renovate bot force-pushed the renovate/major-typescript branch from f6c77b1 to ff6cb73 Compare June 1, 2023 20:04
@renovate renovate bot force-pushed the renovate/major-typescript branch 3 times, most recently from 26a5c29 to 7ff1f21 Compare June 29, 2023 02:15
@renovate renovate bot force-pushed the renovate/major-typescript branch from 7ff1f21 to e108c50 Compare July 12, 2023 20:15
@renovate renovate bot force-pushed the renovate/major-typescript branch from e108c50 to 8a85f03 Compare August 24, 2023 21:01
@renovate renovate bot force-pushed the renovate/major-typescript branch 7 times, most recently from 652489a to 6b4b394 Compare September 13, 2023 01:55
@renovate renovate bot force-pushed the renovate/major-typescript branch from 6b4b394 to 2cfd929 Compare November 20, 2023 20:23
@renovate renovate bot force-pushed the renovate/major-typescript branch from 2cfd929 to bb11e50 Compare December 6, 2023 19:59
@renovate renovate bot force-pushed the renovate/major-typescript branch from bb11e50 to aaa5b4d Compare December 18, 2023 04:54
@renovate renovate bot force-pushed the renovate/major-typescript branch from aaa5b4d to 470a926 Compare December 18, 2023 04:55
@github-actions GitHub Actions
Copy link

Automatically marking pull request as stale due to lack of activity

@github-actions github-actions bot added the stale label Feb 18, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 3, 2024

Automatically closing this pull request as stale

@github-actions github-actions bot closed this Mar 3, 2024
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Mar 3, 2024

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.

@renovate renovate bot deleted the renovate/major-typescript branch March 3, 2024 01:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants