chore: Pin vscode-vue-languageservice to 0.27.26 #473
Merged
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
|
Looks very related: vuejs/language-tools#547, though the fix for that has been released in 0.27.28. I might try creating a smaller repro and open a new issue when I get time... |
eddiekeller
approved these changes
Oct 5, 2021
zchenwei
approved these changes
Oct 5, 2021
2 tasks
2 tasks
thaddmt
pushed a commit
that referenced
this pull request
Apr 7, 2023
Sync amplify-ui to amplify-ui-staging
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue #, if available:
Description of changes: I was able to narrow down the recent vue failures to upstream dependency
vscode-vue-languageservice.vue-tscdepends onvscode-vue-languageservice@^0.27.0, which got bumped as its semver is denoted by carets. Pinning this version to 0.27.26 to resolve CI. Will check their repo for related issues.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.