Skip to content

Bump @types/vscode from 1.86.0 to 1.97.0#64

Open
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/npm_and_yarn/types/vscode-1.97.0
Open

Bump @types/vscode from 1.86.0 to 1.97.0#64
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/npm_and_yarn/types/vscode-1.97.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Feb 10, 2025

Bumps @types/vscode from 1.86.0 to 1.97.0.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@types/vscode](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/vscode) from 1.86.0 to 1.97.0.
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/vscode)

---
updated-dependencies:
- dependency-name: "@types/vscode"
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Feb 10, 2025
Comment thread package-lock.json
"integrity": "sha512-ueE73loeOTe7olaVyqP9mrRI54kVPJifUPjblZo9fYcv1CuVLPOEKEkqW0GkqPC454+nCEoigLWnC2Pp7prZ9w==",
"dev": true
},
"@ungap/structured-clone": {
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Code improvements:

    • Updated "@types/vscode" version from "^1.86.0" to "^1.97.0" in package.json and yarn.lock to keep dependencies up to date.
    • Added license field for "@types/vscode" in yarn.lock.
  • Bug risks:

    • No critical bug risks observed in the provided code snippet.

Overall, the changes made seem appropriate for updating the TypeScript definitions for Visual Studio Code ("@types/vscode") to version 1.97.0, keeping the project's dependencies aligned with the latest available versions.

Comment thread package.json
"@types/vscode": "^1.97.0",
"@vscode/test-electron": "^2.3.8",
"eslint": "^8.57.0",
"glob": "^10.3.10",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Upgrade the "@types/vscode" from version ^1.86.0 to ^1.97.0 in the package.json file.

By upgrading the "@types/vscode" to the latest version (^1.97.0), you can benefit from any bug fixes, additional typings, and features that may have been introduced since version 1.86.0. It's always good to stay up to date with the latest typings for better compatibility and functionality.

  1. No other apparent issues or bugs in this code snippet.

  2. Remember to run your test suite after making this change to ensure that everything still works as expected.

Overall, ensuring that your dependencies are up to date is a good practice to maintain the stability and security of your project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants