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 yeoman-assert.
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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage increased (+0.02%) to 98.002% when pulling 23ba52a9b3feaed68aa90c8801f8fc14dd658ace on greenkeeper-yeoman-assert-3.0.0 into 53f0beec9ad9a33a9f6b47649ca34a4d6bae95f8 on master.
Hello lovely humans,
yeoman-assert just published its new version 3.0.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 yeoman-assert. 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 :sparkles:
You rock!
:palm_tree:
GitHub Release
The new version differs by 18 commits .
b6dc645
3.0.0
7d2945b
Add eslint as dev dependency
446ff2d
Remove last dependency by es6-ing a line of code
69639ae
reduce dependencies and code complexity (#20)
41b7f28
Update dependencies to enable Greenkeeper 🌴 (#22)
ed7f3f0
2.2.2
23e82a5
Fix #21 objectContent with null value
718319c
Add tests for .textEqual() (#18)
d805352
2.2.1
ecec448
fix aliasing for (no)jsonFileContent aliases (#17)
6671839
2.2.0
4db399e
Add assert.noObjectContent() and assert.noJsonFileContent() (#16)
aa6a727
2.1.2
5d4e4c8
Merge pull request #14 from kierans/master
859d0dd
Fixes yeoman/yeoman-assert#13
There are 18 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.