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

chore(deps): update dependency vscode-json-languageservice to v5.3.11 #2446

Merged
merged 1 commit into from Apr 23, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 22, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vscode-json-languageservice 5.3.10 -> 5.3.11 age adoption passing confidence

Release Notes

Microsoft/vscode-json-languageservice (vscode-json-languageservice)

v5.3.11

Compare Source


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.

Copy link

socket-security bot commented Apr 22, 2024

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher

View full report↗︎

@renovate renovate bot force-pushed the renovate/vscode-json-languageservice-5.x-lockfile branch 2 times, most recently from ef66e86 to ff3dc1d Compare April 23, 2024 01:33
@renovate renovate bot force-pushed the renovate/vscode-json-languageservice-5.x-lockfile branch from ff3dc1d to b3809fe Compare April 23, 2024 03:12
@mcollina mcollina merged commit 1855ba4 into main Apr 23, 2024
87 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.

None yet

1 participant