The version 4.0.2 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 chai.
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 Notes4.0.2 / 2017-06-05
We have another bugfix release, addressing some issues for WebPack 1 users.
Bug Fixes
Revert getting version information from package.json, some bundler tools like Webpack do not come default with json loaders despite Node being able to handle this. This change moves back to hardcoding the version number in the codebase. (#985, #986)
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).
Coverage remained the same at 100.0% when pulling 19ac8de7f2fa07db6e2437fa63f495b6771fb6c6 on greenkeeper/chai-4.0.2 into 37aa483ab208ffb29fe0cc54915bd536dc293b86 on master.
We have another bugfix release, addressing some issues for WebPack 1 users.
Bug Fixes
Revert getting version information from package.json, some bundler tools like Webpack do not come default with json loaders despite Node being able to handle this. This change moves back to hardcoding the version number in the codebase. (#985, #986)
Version 4.0.2 of chai just got published.
The version 4.0.2 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 chai. 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
4.0.2 / 2017-06-05We have another bugfix release, addressing some issues for WebPack 1 users.
Bug Fixes
Commits
The new version differs by 353 commits.
616cf8b
Revert get version package json (#986)
b38b8d7
fix: (#978) remove browser field (#982)
d0ace69
Update supported node version badge in README FIX #975
ab1fbad
Merge pull request #973 from chaijs/chore-uncomment-travis-deploy
545ca2f
chore: uncomment travis lines
6349ff4
Merge pull request #972 from lucasfcosta/release-4.0.0
0fe98b1
chai@4.0.0
30a4451
Merge pull request #967 from lucasfcosta/remove-lib-bump
8ba95a7
Remove bump command to change lib/chai.js
0825826
Merge pull request #964 from zetamorph/assert-nestedInclude-ownInclude
f3adfd9
fix: PhantomJS 1.x incompatibility (#966)
b744130
Assert: made documentation more descriptive
33e4403
test: added custom message test to negated .nested-, .deep-, .own.include
4180242
test: added message argument to negated nested-, deep-, own- and deepOwnInclude
40bb490
assert interface: add .deepOwnInclude and notdeepOwnInclude
There are 250 commits in total.
See 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: