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.

Sign up for GitHub

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

Jump to bottom

An in-range update of vscode-languageserver-protocol is breaking the build 🚨 #124

Closed
greenkeeper bot opened this issue Sep 11, 2018 · 1 comment
Closed

An in-range update of vscode-languageserver-protocol is breaking the build 🚨 #124

greenkeeper bot opened this issue Sep 11, 2018 · 1 comment
Labels
greenkeeper

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Sep 11, 2018

Version 3.13.0 of vscode-languageserver-protocol was just published.

Branch Build failing 🚨
Dependency vscode-languageserver-protocol
Current Version 3.12.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

vscode-languageserver-protocol is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
  • ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).
FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Sep 11, 2018

After pinning to 3.12.0 your tests are passing again. Downgrade this dependency 📌.

@Turbo87 Turbo87 closed this as completed Dec 10, 2018
saravanak pushed a commit to saravanak/ember-language-server that referenced this issue Jun 29, 2020
@lifeart
bugfix: fix pod-like components naming with "component" word in name (e…
86bf37c 
…mber-tooling#124)

* bugfix: fix pod-like components naming with "component" word in name

* chore: updates from comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
greenkeeper
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Turbo87