This repository was archived by the owner on Nov 21, 2025. It is now read-only.
build: update language-service version and bump version for release #2154
+7,061
−4,598
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updates the language-service version to fix issues like: #2153 Bumps the version of the repository so that we can cut a new VSCode extension release.
crisbeto
approved these changes
Mar 13, 2025
Member
Author
|
Verified locally that all tests pass (because CI is probably still OOM-ing currently) |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the language-service version to fix issues like: #2153
Bumps the version of the repository so that we can cut a new VSCode extension release.
I've verified locally that this fixes the issues as expected. We just didn't have a extension release with the latest version.