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

An in-range update of vscode is breaking the build 🚨 #35

Open
greenkeeper bot opened this issue Dec 4, 2018 · 12 comments
Open

An in-range update of vscode is breaking the build 🚨 #35

greenkeeper bot opened this issue Dec 4, 2018 · 12 comments
Assignees

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 4, 2018

The devDependency vscode was updated from 1.1.22 to 1.1.23.

🚨 View failing branch.

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

vscode 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 failed (Details).

Commits

The new version differs by 4 commits.

See the full diff

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 Dec 4, 2018

  • The devDependency vscode was updated from 1.1.23 to 1.1.24.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 4, 2018

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

@bengreenier bengreenier self-assigned this Dec 5, 2018
@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 5, 2018

  • The devDependency vscode was updated from 1.1.24 to 1.1.25.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 1 commits.

  • 163aa90 Remove gulp-symdest dependency (fixes #123)

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 6, 2018

  • The devDependency vscode was updated from 1.1.25 to 1.1.26.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 2 commits.

  • e5d9f33 actually remove gulp-symdest (bump@1.1.26)
  • 163aa90 Remove gulp-symdest dependency (fixes #123)

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Feb 7, 2019

  • The devDependency vscode was updated from 1.1.28 to 1.1.29.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 9 commits.

  • ea86293 vscode@1.1.29
  • aafb824 disable other extensions in testing (#142)
  • 5101059 bump to 1.1.28
  • df6aedf More mocha options support (#141)
  • 5815a93 bump to 1.1.27
  • e05bf6a share request options
  • 9610330 Add locale argument for running with VS Code (#139)
  • e5d9f33 actually remove gulp-symdest (bump@1.1.26)
  • 163aa90 Remove gulp-symdest dependency (fixes #123)

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Feb 21, 2019

  • The devDependency vscode was updated from 1.1.29 to 1.1.30.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 11 commits.

  • e81d78a bump@1.1.30
  • 4f6e30d Support passing user-data-dir to tests (#144)
  • ea86293 vscode@1.1.29
  • aafb824 disable other extensions in testing (#142)
  • 5101059 bump to 1.1.28
  • df6aedf More mocha options support (#141)
  • 5815a93 bump to 1.1.27
  • e05bf6a share request options
  • 9610330 Add locale argument for running with VS Code (#139)
  • e5d9f33 actually remove gulp-symdest (bump@1.1.26)
  • 163aa90 Remove gulp-symdest dependency (fixes #123)

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 20, 2019

  • The devDependency vscode was updated from 1.1.30 to 1.1.31.

Your tests are still failing with this version. Compare changes

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 20, 2019

  • The devDependency vscode was updated from 1.1.31 to 1.1.32.

Your tests are still failing with this version. Compare changes

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 21, 2019

  • The devDependency vscode was updated from 1.1.32 to 1.1.33.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 6, 2019

  • The devDependency vscode was updated from 1.1.33 to 1.1.34.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jun 26, 2019

  • The devDependency vscode was updated from 1.1.34 to 1.1.35.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jul 31, 2019

  • The devDependency vscode was updated from 1.1.35 to 1.1.36.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 15 commits.

  • 0090df8 v1.1.36
  • 50e9a97 Add a migration notice
  • 1688fb3 Use an accurate repository field in package.json (#160)
  • f6fef4d v1.1.35
  • a6da027 Upgrade to mocha@5. Fix microsoft/vscode#75732
  • 38c68ad update @types/node
  • 9489901 v1.1.34
  • bcb4b8a Upgrade vscode-test dependency
  • 10007a7 v1.1.33
  • df9c929 Drop dead code
  • 26a6775 Update vscode-test deps
  • c54e6b7 Clean up for #155
  • b38bba3 Merge pull request #155 from gkalpak/fix-test-use-correct-version
  • 59f742e fix(test): take CODE_VERSION into account when downloading VSCode
  • cdb897e fix(test): look for existing VSCode app in the correct directory

See the full diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant