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 source-map-support is breaking the build 🚨 #7

Open
greenkeeper bot opened this issue Aug 17, 2017 · 3 comments
Open

Comments

@greenkeeper
Copy link

greenkeeper bot commented Aug 17, 2017

Version 0.4.16 of source-map-support just got published.

Branch Build failing 🚨
Dependency source-map-support
Current Version 0.4.15
Type devDependency

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

As source-map-support 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
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 9 commits.

  • 6c3f308 0.4.16
  • 2c8176b Update compiled file
  • 9addc16 Merge pull request #138 from Yogu/fix-out-of-range-columns
  • 6020c02 Merge pull request #187 from evanw/update-travis
  • d74b70d Fix tests on Node.js >=8.4
  • 7cfd425 Add all supported releases to Travis
  • df2d24f Merge pull request #185 from tisba/patch-1
  • 77b7f52 updates link in README to V8 Stack Trace API
  • 58a1169 Defensive coding to prevent out-of-range column

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 Aug 17, 2017

After pinning to 0.4.15 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@greenkeeper
Copy link
Author

greenkeeper bot commented Sep 2, 2017

Version 0.4.17 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 3 commits.

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Sep 10, 2017

Version 0.4.18 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 4 commits.

  • b9b5a55 0.4.18
  • 35c4633 Update compiled file
  • dda2727 Merge pull request #191 from tapjs/master
  • 43d0b80 Be resilient against readFileSync failures

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