Update chai to the latest version 馃殌 #598
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
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
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 4.1.0 of chai just got published.
The version 4.1.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 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.1.0 / 2017-07-11This release includes one new feature and a few bug fixes.
New Features
Bug Fixes
.propertyassertion (#992; @meeber)Chores
expectTypesto accessssfiflag (#993; @meeber)Commits
The new version differs by 16 commits.
df9073cMerge pull request #998 from v1adko/make-releasecad9933Merge pull request #1004 from chaijs/code-ownerscf70b11Create CODEOWNERS3397ddaMerge pull request #1005 from meeber/skip-failing-tests11a6f85test: skip failing.includetests in IE1145cb327chai@4.1.02eddd79Add ES6 collection support to include() (#994)3c932e2feat: allow dates for isBelow and isAbove assertions (#990)3bcb21cMerge pull request #979 from chaijs/greenkeeper/browserify-14.4.05daceabMerge pull request #988 from samlanning/missing-var9116bc8Merge pull request #993 from meeber/refactor-expect-types351e968Merge pull request #992 from meeber/property-target-typee7b2384refactor:expectTypesto accessssfiflage6ddf64fix: check target's type in.propertyassertion7e466afAdd a missing var keyword found by lgtm.comThere are 16 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 馃尨