An in-range update of gulp-sourcemaps is breaking the build 🚨
greenkeeper opened this issue · comments
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 💪
Status Details
Commits
The new version differs by 5 commits .
23db837Merge branch '1.X'e7c2e96bump0c3fa97soureRoot should not be set for file.base, sourceRoot is just a mapping in the browser0e5cf97Merge branch '1.X'f4393d0less 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 and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
After pinning to 2.2.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 2.3.1 just got published.
Your tests are still failing with this version. Compare the changes 🚨
Commits
The new version differs by 10 commits .
2b2a275bump 2.3.1 for mapSouces bug fix issue #270d7c99a7bump for bug fix for mapping sources correctly0afd11cbug fix issue #270faa0614bump 2.2.3 -> 2.3.08299abebump 1.9 -> 1.10fc16decMerge branch '1.X'ba7d7fcRefactoring:1f13876Merge branch '1.X'5c6bb18increasing timeout for travis53a426battempt to fix 0.12.X node specs
See the full diff.
Version 2.4.0 just got published.
Your tests are still failing with this version. Compare the changes 🚨
Version 2.4.1 just got published.
Your tests are still failing with this version. Compare the changes 🚨