The version 3.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of travis-deploy-once.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Accept a travisOpts parameter, instead of fetching github repo (7c4a2a5), closes #2
BREAKING CHANGES
The plugin does not call the Github API anymore to
determine if the regular or the pro version of the Travis API should be
called.
The new travisOpts parameter is added in is passed to the Travis
client API.
Use travisDeployOnce({travisOpts: {pro: true}}) to call the pro version
of the API.
Commits
The new version differs by 4 commits.
7c4a2a5feat: Accept a travisOpts parameter, instead of fetching github repo
1f97ca1chore(package): update prettier to version 1.7.2
7451c72chore(package): update sinon to version 4.0.0
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).
Version 3.0.0 of travis-deploy-once just got published.
The version 3.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of travis-deploy-once. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v3.0.03.0.0 (2017-10-02)
Features
BREAKING CHANGES
determine if the regular or the pro version of the Travis API should be
called.
The new
travisOptsparameter is added in is passed to the Travisclient API.
Use
travisDeployOnce({travisOpts: {pro: true}})to call the pro versionof the API.
Commits
The new version differs by 4 commits.
7c4a2a5feat: Accept a travisOpts parameter, instead of fetching github repo1f97ca1chore(package): update prettier to version 1.7.27451c72chore(package): update sinon to version 4.0.0b9958c6ci(codecov): Enforce coverage with CodecovSee 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: