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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of @octokit/rest is breaking the build 馃毃 #1002

greenkeeper bot opened this issue Sep 3, 2019 · 3 comments


Copy link

commented Sep 3, 2019

The dependency @octokit/rest was updated from 16.28.8 to 16.28.9.

馃毃 View failing branch.

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

@octokit/rest is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v16.28.9

16.28.9 (2019-09-03)

Bug Fixes

  • package: update universal-user-agent to version 4.0.0 (b5a96a9)

The new version differs by 3 commits.

  • ee57e51 refactor: adapt for universal-user-agent@v4
  • 981597d chore(package): update lockfile package-lock.json
  • b5a96a9 fix(package): update universal-user-agent to version 4.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don鈥檛 help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 馃尨

@greenkeeper greenkeeper bot added the greenkeeper label Sep 3, 2019

@issue-label-bot issue-label-bot bot added the bug 馃悶 label Sep 3, 2019


This comment has been minimized.

Copy link

commented Sep 3, 2019

Issue-Label Bot is automatically applying the label bug 馃悶 to this issue, with a confidence of 0.90. Please mark this comment with 馃憤 or 馃憥 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.


This comment has been minimized.

Copy link
Contributor Author

commented Sep 3, 2019

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


This comment has been minimized.

Copy link

commented Sep 3, 2019

@gr2m gr2m closed this Sep 3, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can鈥檛 perform that action at this time.