browser-sync just published its new version 2.18.2.
State
Failing tests :rotating_light:
Dependency
browser-sync
New version
2.18.2
Type
devDependency
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As browser-sync 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:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Coverage remained the same at 85.083% when pulling f2c8c99175e7c7fe3ae89c484d2efbeeb4cd81a8 on greenkeeper-browser-sync-2.18.2 into 9e6ae094509f5c091252b5abd5b6a63ef33f602a on master.
Coverage remained the same at 85.083% when pulling 93e5a4e09b81881c0e339c776aadfa3c726bba72 on greenkeeper-browser-sync-2.18.2 into 025393ddedb01a7e7ea84ac85d584527a7f20907 on master.
Coverage remained the same at 85.083% when pulling 005941003b09e453811e00d14675e3ca61ec3718 on greenkeeper-browser-sync-2.18.2 into b66e00e562dfd05f3818e43debc3c5016850a96e on master.
Coverage remained the same at 85.083% when pulling 005941003b09e453811e00d14675e3ca61ec3718 on greenkeeper-browser-sync-2.18.2 into b66e00e562dfd05f3818e43debc3c5016850a96e on master.
Hello lovely humans,
browser-sync just published its new version 2.18.2.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As browser-sync 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:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
The new version differs by 30 commits .
d979876
2.18.2
3aced70
Merge branch 'alexturpin'
8dd9f01
tests: fix opn stubs
f3b921b
chore: doc blocks
15e0f1e
Merge branch 'master' of https://github.com/alexturpin/browser-sync into alexturpin
42bab46
2.18.1
d4cedbc
fix(httpModule): only lookup in local directory
81c3f74
2.18.0
09c938b
docs: Since param on httpModule option
67d58ef
Merge pull request #1250 from BrowserSync/AddSupportForOverridingHttpModule
8ba178e
feat(httpModule): Allow custom HTTP module to be given in options
5136fd5
Merge branch 'AddSupportForOverridingHttpModule' of github.com:itslenny/browser-sync into AddSupportForOverridingHttpModule
4af1a4d
test: skip tunnel e2e (flaky ci) & use url directly in supertest requests to SSL endpoints
558c6da
Allow users to override default httpModule
eaaa715
2.17.6
There are 30 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade