Update gh-pages to version 0.12.0 🚀 #880
Merged
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
Current coverage is 100% (diff: 100%)@@ master #880 diff @@
====================================
Files 137 137
Lines 2259 2259
Methods 0 0
Messages 0 0
Branches 0 0
====================================
Hits 2259 2259
Misses 0 0
Partials 0 0
|
|
This needs manually tested before merging. |
9111457 to
dc73b14
Compare
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.
Hello lovely humans,
gh-pages just published its new version 0.12.0.
This version 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 gh-pages.
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.
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 ✨
You rock!
🌴
The new version differs by 40 commits .
c6cd05d0.12.0ffc8d6aLog changes33815e4Merge pull request #146 from tschaub/updatesb7e8779Merge pull request #138 from sobolevn/patch-1f8a7f4cUpdate dependenciesb424c0fTest on Node 6 and cache dependencies7bc6da9Update dev dependencies49e48a4Unindentab5c4e5Merge pull request #142 from tschaub/greenkeeper-globby-6.1.0fd9e5cfchore(package): update globby to version 6.1.0d1dbe48Updated readme.md with svg image4d5a4a6Merge pull request #134 from tschaub/greenkeeper-eslint-3.8.0de66f8bMerge pull request #135 from tschaub/greenkeeper-async-2.1.279b1aa9chore(package): update async to version 2.1.2494db0echore(package): update eslint to version 3.8.0There are 40 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade