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.

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

Update dependency typescript to v3.9.10 #90

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 24, 2023

Mend Renovate

This PR contains the following updates:

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

Release Notes

Microsoft/TypeScript (typescript)

v3.9.10: TypeScript 3.9.10

Compare Source

This release ships both an overall performance improvement, along with a mitigation for a performance regression when upgrading to Node.js 16. See the change for more details.

v3.9.9: TypeScript 3.9.9

Compare Source

This release contains a fix for an issue when language service plugins have no specified name.

v3.9.8: TypeScript 3.9.8

Compare Source

This release contains fixes for a security risk involving language service plugin loading. More details are available here.

v3.9.7: TypeScript 3.9.7

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

This release contains a fix for CVE-2020-1416

(note, 3.9.4 was intentionally skipped due to minor complications in publishing)

Downloads are available on:

v3.9.6: TypeScript 3.9.6

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

(note, 3.9.4 was intentionally skipped due to minor complications in publishing)

Downloads are available on:

v3.9.5: TypeScript 3.9.5

This release contains bug fixes in type-checking, emit, and editor scenarios.

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

(note, 3.9.4 was intentionally skipped due to minor complications in publishing)

Downloads are available on:

v3.9.3: TypeScript 3.9.3

Compare Source

This release contains bug fixes in type-checking, APIs, emit, and editor scenarios.

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v3.9.2: TypeScript 3.9.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:

v3.8.3: TypeScript 3.8.3

Compare Source

For release notes, check out the release announcement.

For new features, check out the What's new in TypeScript v3.8.

For the complete list of fixed issues, check out the

Downloads are available on:

v3.8.2: TypeScript 3.8.2

Compare Source

For release notes, check out the release announcement.

For new features, check out the What's new in TypeScript v3.8.2.

For the complete list of fixed issues, check out the

Downloads are available on:

v3.7.7: TypeScript 3.7.7

Compare Source

This release contains a fix for an issue when language service plugins have no specified name.

v3.7.6: TypeScript 3.7.6

Compare Source

This release contains fixes for a security risk involving language service plugin loading. More details are available here.

v3.7.5: TypeScript 3.7.5

Compare Source

For the complete list of fixed issues, check out the

v3.7.4: TypeScript 3.7.4

Compare Source

For the complete list of fixed issues, check out the

Downloads are available on:

v3.7.3: TypeScript 3.7.3

Compare Source

For the complete list of fixed issues, check out the

Downloads are available on:

v3.7.2: TypeScript 3.7.2

Compare Source

For release notes, check out the release announcement.

For new features, check out the What's new in TypeScript v3.7.2.

For the complete list of fixed issues, check out the

Downloads are available on:

v3.6.5: TypeScript 3.6.5

Compare Source

This patch fixes an issue where TypeScript would erroneously report the following error under noImplicitAny when encountering a private get accessor in a .d.ts file.

Property 'myGetter' implicitly has type 'any', because its get accessor lacks a return type annotation.

This is an issue when using packages published from TypeScript 3.7 and newer. Users can upgrade to 3.6.5 to fix the issue.

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v3.6.4: TypeScript 3.6.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:

v3.6.3: TypeScript 3.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:

v3.6.2: TypeScript 3.6.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:


Configuration

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

🚦 Automerge: Enabled.

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 has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Author

renovate bot commented Mar 24, 2023

⚠ 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
Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

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.

None yet

0 participants