Skip to content

Update jest-each to the latest version 🚀 #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 7, 2017

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Sep 6, 2017

Version 0.3.1 of jest-each just got published.

Dependency jest-each
Current Version 0.3.0
Type devDependency

The version 0.3.1 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 jest-each.
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 v0.3.1

Patch

  • Add demo to readme
  • Update project badges
Commits

The new version differs by 3 commits.

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 🌴

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 4f82a79 on greenkeeper/jest-each-0.3.1 into df51b12 on master.

@mattphillips mattphillips merged commit cfe7379 into master Sep 7, 2017
@mattphillips mattphillips deleted the greenkeeper/jest-each-0.3.1 branch September 7, 2017 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants