-
Notifications
You must be signed in to change notification settings - Fork 3
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 ngrok is breaking the build 🚨 #243
Comments
Version 2.2.8 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 |
Version 2.2.9 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 |
Version 2.2.11 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 11 commits.
See the full diff |
Version 2.2.12 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 12 commits.
See the full diff |
Version 2.2.13 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 12 commits.
See the full diff |
Version 2.2.14 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 16 commits.
There are 16 commits in total. See the full diff |
Version 2.2.15 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 18 commits.
There are 18 commits in total. See the full diff |
Version 2.2.16 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 23 commits.
There are 23 commits in total. See the full diff |
Version 2.2.17 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 25 commits.
There are 25 commits in total. See the full diff |
Version 2.2.18 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 27 commits.
There are 27 commits in total. See the full diff |
Version 2.2.19 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 29 commits.
There are 29 commits in total. See the full diff |
Version 2.2.20 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 31 commits.
There are 31 commits in total. See the full diff |
Version 2.2.21 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 35 commits.
There are 35 commits in total. See the full diff |
Version 2.2.22 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 37 commits.
There are 37 commits in total. See the full diff |
Version 2.2.23 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 39 commits.
There are 39 commits in total. See the full diff |
Version 2.2.24 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 41 commits.
There are 41 commits in total. See the full diff |
Version 2.2.25 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 43 commits.
There are 43 commits in total. See the full diff |
Version 2.2.26 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 48 commits.
There are 48 commits in total. See the full diff |
Version 2.3.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 49 commits.
There are 49 commits in total. See the full diff |
Version 2.2.7 of ngrok just got published.
This version is covered by your current version range and after updating it in your project the build failed.
ngrok is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/Kibibit/kibibit-code-editor/builds/226814962?utm_source=github_status&utm_medium=notification)Commits
The new version differs by 1 commits0.
c1a4b27
closes #76 - handle web_addr:false with proper error
false
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: