molecuel / core

Molecuel core module
MIT License
4 stars 1 forks source link

An in-range update of gulp-sourcemaps is breaking the build 🚨 #4

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 2.2.3 of gulp-sourcemaps just got published.

Branch Build failing 🚨
Dependency gulp-sourcemaps
Current Version 2.2.2
Type devDependency

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

As gulp-sourcemaps is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:


Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/molecuel/mlcl_core/builds/190156309)
Commits

The new version differs by 5 commits .

  • 23db837 Merge branch '1.X'
  • e7c2e96 bump
  • 0c3fa97 soureRoot should not be set for file.base, sourceRoot is just a mapping in the browser
  • 0e5cf97 Merge branch '1.X'
  • f4393d0 less integration test proves that it compiles in a reasonable amount of time with sourcemaps

See the full diff.

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

After pinning to 2.2.2 your tests are passing again. Downgrade this dependency 📌.

DominicBoettger commented 7 years ago

Time collision while upgrading to different files.