Open greenkeeper[bot] opened 7 years ago
After pinning to 1.1.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
The new version differs by 8 commits.
cc9b685
bump to 1.1.6
6500337
Merge pull request #79 from JimiC/update_depends
5133655
Revert @types/node to v7.
23aba69
Update all dependencies.
9d39419
Merge pull request #80 from JimiC/ignore_fix_cleanup
4814cad
Clean up and adds more files/folders to be ignored.
86f9f59
Merge pull request #75 from donaldpipowitch/patch-1
5be321a
added bin
See the full diff
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
Your tests are still failing with this version. Compare the changes π¨
devDependency
vscode was updated from 1.1.21
to 1.1.22
.Your tests are still failing with this version. Compare changes
devDependency
vscode was updated from 1.1.23
to 1.1.24
.Your tests are still failing with this version. Compare changes
devDependency
vscode was updated from 1.1.24
to 1.1.25
.Your tests are still failing with this version. Compare changes
devDependency
vscode was updated from 1.1.25
to 1.1.26
.Your tests are still failing with this version. Compare changes
Version 1.1.1 of vscode just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As vscode is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this :muscle:
Status Details
- β **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/fforjan/vs-solution-support/builds/247410340?utm_source=github_status&utm_medium=notification)Commits
The new version differs by 7 commits.
4da0d7b
bump 1.1.1
6352382
Merge pull request #67 from bvandre/master
fce149d
use npm https proxy config when using https protocol
9007462
honor npm config proxy settings
8216ce9
mention docs
69be7f0
:lipstick: readme
4299e7b
readme
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: