Swydo / blaze-apollo

Blaze integration for the Apollo Client
MIT License
54 stars 6 forks source link

An in-range update of standard-version is breaking the build 🚨 #21

Open greenkeeper[bot] opened 4 years ago

greenkeeper[bot] commented 4 years ago

The devDependency standard-version was updated from 7.0.1 to 7.1.0.

🚨 View failing branch.

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

standard-version is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/Swydo/blaze-apollo/builds/640171450?utm_source=github_status&utm_medium=notification)).

Commits

The new version differs by 22 commits.

  • 5c80907 chore(release): 7.1.0
  • 00512d0 revert: "chore(deps): bump conventional-changelog to v3.1.17"
  • 8168e51 ci(travis): add node 12 to testing matrix
  • d1480bd chore(deps): bump conventional-changelog to v3.1.17
  • 0273809 docs: correct link in readme
  • ba80a0c feat: Adds support for header (--header) configuration based on the spec. (#364)
  • bc606f8 fix(deps): update dependency conventional-changelog-conventionalcommits to v4.2.3 (#496)
  • 0e74e26 chore(deps): update dependency eslint to v6.7.2 (#444)
  • 3bbab00 chore(deps): update dependency mocha to v6.2.2 (#458)
  • d97e446 chore(deps): update dependency eslint-plugin-node to v10 (#451)
  • 35b90c3 fix(deps): update dependency yargs to v15 (#484)
  • 564d948 feat: custom 'bumpFiles' and 'packageFiles' support (#372)
  • d557372 fix: use require.resolve for the default preset (#465)
  • f3e6944 test: add a case for loading a configuration (issueUrlFormat) from package.json. (#486)
  • 995e592 chore(deps): update dependency coveralls to v3.0.9 (#489)

There are 22 commits in total.

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 4 years ago

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