The version 2.5.3 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 log4js.
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.
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).
Version 2.5.3 of log4js was just published.
The version 2.5.3 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 log4js.
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 13 commits.
d0b630a2.5.382d0602Merge pull request #661 from barwin/barwin/redis-appender-shutdown2a28437feat(redis): quit on log4js.shutdown05ad768Fixed confusing extra letter05ce809Merge pull request #656 from tmihalcin/webpack-workaroundf55702eUpdate webpack.mdeac84c4docs: webpack workaround doc069d94afix(coverage): coverage report was failing due to wrong path in test822ca2e2.5.2fc9e257Merge pull request #653 from log4js-node/levels-before-configuredf58b2afix(#652): access levels before configure is called0078bad2.5.1abe6e3cfix(types): fix for missing types #651See 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: