Skip to content

Conversation

@greenkeeperio-bot
Copy link
Contributor

Hello lovely humans,

karma-webpack just published its new version 2.0.1.

State Update 🚀
Dependency karma-webpack
New version 2.0.1
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 karma-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

  • Fix for publishing error

The new version differs by 5 commits .

  • 24b3f3c chore(release): karma-webpack v2.0.1
  • 1f13a86 chore(release): karma-webpack v2.0.0
  • 9fd5fdf chore(package): update webpack peerDependencies
  • 70dbb24 style(lint): lint fixes (#195)
  • 2723439 fix(config): webpack rc4 schema enforcment (fixes #193)

See the full diff.


This pull request was created by greenkeeper.io.

Tired of seeing this sponsor message? ⚡ greenkeeper upgrade

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling b39d7d5 on greenkeeper-karma-webpack-2.0.1 into 63e4214 on master.

@mseemann mseemann force-pushed the greenkeeper-karma-webpack-2.0.1 branch from b39d7d5 to 3e7bf44 Compare February 16, 2017 08:01
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 3e7bf44 on greenkeeper-karma-webpack-2.0.1 into c9f2761 on master.

@mseemann mseemann force-pushed the greenkeeper-karma-webpack-2.0.1 branch from 3e7bf44 to e0fded1 Compare February 20, 2017 13:47
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling e0fded1 on greenkeeper-karma-webpack-2.0.1 into e7227a0 on master.

@mseemann mseemann force-pushed the greenkeeper-karma-webpack-2.0.1 branch from e0fded1 to c4db51d Compare February 20, 2017 14:43
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling c4db51d on greenkeeper-karma-webpack-2.0.1 into 1756db3 on master.

@mseemann mseemann force-pushed the greenkeeper-karma-webpack-2.0.1 branch from c4db51d to 5dbf820 Compare February 20, 2017 14:55
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 5dbf820 on greenkeeper-karma-webpack-2.0.1 into b9385ae on master.

@mseemann mseemann force-pushed the greenkeeper-karma-webpack-2.0.1 branch from 5dbf820 to 743f1b2 Compare February 20, 2017 15:46
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 743f1b2 on greenkeeper-karma-webpack-2.0.1 into d2126b9 on master.

@mseemann mseemann closed this Feb 20, 2017
@mseemann mseemann deleted the greenkeeper-karma-webpack-2.0.1 branch February 20, 2017 15:53
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.

3 participants