Skip to content
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

An in-range update of babel-loader is breaking the build 🚨 #58

Open
greenkeeper bot opened this issue Feb 14, 2017 · 4 comments
Open

An in-range update of babel-loader is breaking the build 🚨 #58

greenkeeper bot opened this issue Feb 14, 2017 · 4 comments

Comments

@greenkeeper
Copy link

greenkeeper bot commented Feb 14, 2017

Version 6.3.0 of babel-loader just got published.

Branch Build failing 🚨
Dependency babel-loader
Current Version 6.2.10
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-loader is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪


Status Details
  • coverage/coveralls First build on greenkeeper/babel-loader-6.3.0 at 12.808% Details

  • ci/circleci Your tests passed on CircleCI! Details

  • continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes v6.3.0

🚀 New Feature

Allow to override BABEL_ENV/NODE_ENV at loader-level. Useful for isomorphic applications which have separate babel config for client and server.

🐛 Bug Fix

  • Update loader-utils dependency to ^0.2.16 to fix compatibility with webpack 2 (#371) @leonaves

💅 Polish

  • Improve FS caching to do less sync calls which improves performance slightly (#375) @akx
Commits

The new version differs by 10 commits .

  • 877e956 6.3.0
  • 4b3bafa FS caching improvements (#375)
  • 0b19a6d Update loader-utils dependecy to ^0.2.16 (#371)
  • 15881f4 Add env query parameter. (#368)
  • e9e3702 Update yarn.lockk
  • 707f31c chore(package): update eslint-config-babel to version 6.0.0 (#360)
  • 5657f48 chore(package): update eslint-config-babel to version 5.0.0 (#359)
  • 757002a Remove plugin-babel (#358)
  • a7e16da Update eslint-config-babel to the latest version 🚀 (#357)
  • 3900952 Update CHANGELOG.md

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 🌴

@greenkeeper
Copy link
Author

greenkeeper bot commented Feb 15, 2017

Version 6.3.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes v6.3.1

🐛 Bug Fix

  • The new forceEnv options wasn't working as expected (#379) @chrisvasz
Commits

The new version differs by 5 commits .

See the full diff.

@greenkeeper
Copy link
Author

greenkeeper bot commented Feb 16, 2017

Version 6.3.2 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes v6.3.2

😢 Regression

  • forceEnv was interfering with regular environment handling
Commits

The new version differs by 7 commits .

See the full diff.

@greenkeeper
Copy link
Author

greenkeeper bot commented Mar 6, 2017

Version 6.4.0 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes v6.4.0

🚀 New Feature

  • added metadata passing from babel to webpack, which is currently used by react-intl (#398) @Ognian
Commits

The new version differs by 16 commits .

There are 16 commits in total. See the full diff.

@greenkeeper
Copy link
Author

greenkeeper bot commented Mar 16, 2017

Version 6.4.1 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes v6.4.1

🐛 Bug Fix

Commits

The new version differs by 18 commits .

There are 18 commits in total. See the full diff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants