opbeat / opbeat-node

DEPRECATED - See Elastic APM instead: https://github.com/elastic/apm-agent-nodejs
BSD 2-Clause "Simplified" License
153 stars 15 forks source link

An in-range update of express-graphql is breaking the build 🚨 #193

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 0.6.11 of express-graphql just got published.

Branch Build failing 🚨
Dependency express-graphql
Current Version 0.6.7
Type devDependency

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

As express-graphql 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/opbeat/opbeat-node/builds/269663412?utm_source=github_status&utm_medium=notification)

Release Notes v0.6.11

Changes

  • None since v0.6.8. This is just a version bump to troubleshoot a Travis deployment failure.
Commits

The new version differs by 42 commits.

  • 2bdcb26 0.6.11
  • f9b80fc Merge pull request #387 from wincent/glh/travis-alt-fix
  • bb8b2a6 Force install before build to fix Travis NPM deploys
  • f468f29 0.6.10
  • 3d43638 Merge pull request #386 from wincent/glh/travis-fix
  • 90aa430 Attempt fix for Travis failure to deploy to NPM
  • deb516c 0.6.9
  • 937aeea 0.6.8
  • d573a4b Merge pull request #384 from wincent/glh/pretty
  • 193fc6d npm run pretty
  • 9071b56 Merge pull request #383 from wincent/glh/graphql-update
  • e9169a3 Update graphql dependency
  • 5f4e9a0 Merge pull request #381 from chentsulin/patch-11
  • bcd47b8 Merge pull request #380 from chentsulin/patch-10
  • c822270 fix a typo

There are 42 commits in total.

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 0.6.7 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.