Update greenkeeper-postpublish to the latest version 🚀 #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 2.0.0 just got published.Update to this version instead 🚀 Release Notesv2.0.02.0.0 (2018-08-17)Features
BREAKING CHANGES
Usage: greenkeeper-postpublish |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 1.4.0 of greenkeeper-postpublish was just published.
The version 1.4.0 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 greenkeeper-postpublish.
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
v1.4.01.4.0 (2018-08-16)
Features
Commits
The new version differs by 21 commits.
114129achore: npm is node6+ now, lets go with this for now946b09dfeat: always have latest npm on CI43c0578feat: newline935ecb9chore: modernice s-r setup327479echore: if we support 0.12, why not keep testing itcb12f0echore: update node versions on travisa5fd6e0Merge pull request #24 from greenkeeperio/greenkeeper/semantic-release-15.9.8c94c5efMerge branch 'master' into greenkeeper/semantic-release-15.9.81846166feat: update standard to 2.88.0fb712ffchore: avoid double buildsfddbcbaMerge pull request #21 from greenkeeperio/greenkeeper/semantic-release-7.0.12c2475dMerge branch 'master' into greenkeeper/semantic-release-7.0.18873fb0Merge pull request #16 from greenkeeperio/greenkeeper/standard-10.0.0-beta.0551f821chore(package): update semantic-release to version 15.9.86deb121chore(package): update semantic-release to version 7.0.1There are 21 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴