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 showdown is breaking the build 🚨 #133

Open
greenkeeper bot opened this issue Nov 2, 2019 · 1 comment
Open

An in-range update of showdown is breaking the build 🚨 #133

greenkeeper bot opened this issue Nov 2, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Nov 2, 2019

The dependency showdown was updated from 1.9.0 to 1.9.1.

🚨 View failing branch.

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

showdown 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 failed (Details).
  • build (12.x): There are 1 failures, 0 warnings, and 0 notices.
  • build (10.x): null
  • build (8.x): There are 1 failures, 0 warnings, and 0 notices.

Release Notes for 1.9.1 (2019-11-02)

1.9.1 (2019-11-02)

Bug Fixes

  • openLinksInNewWindow: add rel="noopener noreferrer" to links (1cd281f), closes #670

Dependecy update

  • yargs: update yargs to latest version ^14.2 (dae65c6)
Commits

The new version differs by 4 commits.

  • 483e51f release 1.9.1
  • 5cc3fcc update dev dependencies
  • 1cd281f fix(openLinksInNewWindow): add rel="noopener noreferrer" to links
  • 58208e5 update dependencies

See the full diff

FAQ and help

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


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Nov 2, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

0 participants