Skip to content

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

grunt-webpack just published its new version 1.0.18.

State Update 🚀
Dependency grunt-webpack
New version 1.0.18
Type devDependency

This version 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 grunt-webpack.
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.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴


GitHub Release

  • Revert configuration support for webpack 2 due to incompatibilities with webpack 1 (Will release grunt-webpack 2.0 which will have support for webpack 2.0)

The new version differs by 3 commits .

  • 78f8031 1.0.18
  • 889f022 Revert "Only pass valid webpack options through to webpack."
  • 99a7a12 Revert "Require pick method from lodash"

See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

@coveralls
Copy link

coveralls commented Oct 10, 2016

Coverage Status

Coverage remained the same at 100.0% when pulling 4bb9b04 on greenkeeper-grunt-webpack-1.0.18 into 8e4e657 on master.

@kumar303 kumar303 force-pushed the greenkeeper-grunt-webpack-1.0.18 branch from 4bb9b04 to 4cbb51a Compare October 11, 2016 22:17
@coveralls
Copy link

coveralls commented Oct 11, 2016

Coverage Status

Coverage remained the same at 100.0% when pulling 4cbb51a on greenkeeper-grunt-webpack-1.0.18 into b8aa29b on master.

@kumar303 kumar303 force-pushed the greenkeeper-grunt-webpack-1.0.18 branch from 4cbb51a to a2b8925 Compare October 11, 2016 22:25
@coveralls
Copy link

coveralls commented Oct 11, 2016

Coverage Status

Coverage remained the same at 100.0% when pulling a2b8925 on greenkeeper-grunt-webpack-1.0.18 into 4724063 on master.

@kumar303 kumar303 force-pushed the greenkeeper-grunt-webpack-1.0.18 branch from a2b8925 to c15c8cb Compare October 15, 2016 19:35
@coveralls
Copy link

coveralls commented Oct 15, 2016

Coverage Status

Coverage remained the same at 100.0% when pulling c15c8cb on greenkeeper-grunt-webpack-1.0.18 into 0bbeec7 on master.

@kumar303 kumar303 force-pushed the greenkeeper-grunt-webpack-1.0.18 branch from c15c8cb to 1b655f3 Compare October 17, 2016 02:20
@kumar303 kumar303 merged commit 76a987f into master Oct 17, 2016
@kumar303 kumar303 deleted the greenkeeper-grunt-webpack-1.0.18 branch October 17, 2016 02:20
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.

4 participants