The version 23.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of ts-jest.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 133 commits.
5000506Merge pull request #600 from kulshekhar/jest-upgrade
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage decreased (-0.4%) to 96.97% when pulling d6acbf885988ef514d069efd8ac1099e011286c4 on greenkeeper/ts-jest-23.0.0 into ad6fc1b7d14ac2645c7dc4660e37adf0266ce3ff on develop.
Coverage decreased (-0.4%) to 96.97% when pulling d6acbf885988ef514d069efd8ac1099e011286c4 on greenkeeper/ts-jest-23.0.0 into ad6fc1b7d14ac2645c7dc4660e37adf0266ce3ff on develop.
Coverage decreased (-0.4%) to 96.97% when pulling d6acbf885988ef514d069efd8ac1099e011286c4 on greenkeeper/ts-jest-23.0.0 into ad6fc1b7d14ac2645c7dc4660e37adf0266ce3ff on develop.
Coverage decreased (-0.4%) to 96.97% when pulling d6acbf885988ef514d069efd8ac1099e011286c4 on greenkeeper/ts-jest-23.0.0 into ad6fc1b7d14ac2645c7dc4660e37adf0266ce3ff on develop.
Version 23.0.0 of ts-jest was just published.
The version 23.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of ts-jest.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 133 commits.
5000506
Merge pull request #600 from kulshekhar/jest-upgrade
4729733
upgrade version
8136977
Merge pull request #599 from kulshekhar/combine-prs
2bfa1fc
update yarn.lock
57a09ee
Merge branch 'greenkeeper/yargs-12.0.1' into combine-prs
5d2115a
resolve conflict
909f072
Merge branch 'greenkeeper/@types/react-16.4.6' into combine-prs
f660121
Merge branch 'js-um/fix-to-work-with-jest-projects-root-path' into combine-prs
6ff8b2c
Merge branch 'catch-syntax-errors' into combine-prs
72c4b21
chore(package): update @types/react to version 16.4.6
390ffcd
fix(package): update yargs to version 12.0.1
e6bcff0
chore(package): update @types/node to version 10.5.1
67659c4
Update @types/node to the latest version 🚀 (#592)
56c3714
Adds test for intentially failing transpilation of TS syntax errors
fbb8c50
Better error message
There are 133 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: