The version 0.0.9 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of airtap.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesv0.0.9
Changed
Upgrade sauce-browsers from ~1.2.0 to ~2.0.0 (@ralphtheninja)
Upgrade commander from ~2.15.1 to ~2.16.0 (@ralphtheninja)
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 0.0.9 of airtap was just published.
The version 0.0.9 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of airtap.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v0.0.9Changed
sauce-browsers
from~1.2.0
to~2.0.0
(@ralphtheninja)commander
from~2.15.1
to~2.16.0
(@ralphtheninja)Added
--coverage
cli option to export browser coverage to.nyc-output/
folder (@vweevers)Removed
--no-coverage
cli option (@vweevers)--no-instrument
cli option (@vweevers)Commits
The new version differs by 14 commits.
873b61b
0.0.9
87f76c3
Prepare 0.0.9 (#196)
ec4aff6
Merge pull request #199 from airtap/allow-retry-in-test
cbd8d25
test sauce integration with mock webdriver
92ee469
account for retries in integration test
aa10b3b
fix(package): update commander to version 2.16.0 (#193)
65be371
Merge pull request #194 from airtap/coverage
58077f2
have client post coverage on test end
82faa78
add route to post coverage (replaces istanbul-middleware)
1fda3aa
support --coverage without --local
3de1e2c
remove --[no-]instrument option
a4d8b1f
disable coverage by default
8b5a723
Merge pull request #192 from airtap/greenkeeper/sauce-browsers-2.0.0
680cede
fix(package): update sauce-browsers to version 2.0.0
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: