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

[Snyk] Upgrade vscode-languageclient from 9.0.0 to 9.0.1 #84

Merged
merged 1 commit into from
Jan 12, 2024

Conversation

sarvex
Copy link

@sarvex sarvex commented Jan 10, 2024

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade vscode-languageclient from 9.0.0 to 9.0.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 3 months ago, on 2023-09-26.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Snyk has created this PR to upgrade vscode-languageclient from 9.0.0 to 9.0.1.

See this package in npm:


See this project in Snyk:
https://app.snyk.io/org/sarvex/project/acfc9d5b-b24b-4997-8ad0-91638504ed45?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

sonarcloud bot commented Jan 10, 2024

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@sarvex sarvex merged commit 3aff421 into main Jan 12, 2024
8 of 9 checks passed
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.

2 participants