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 markdown-it is breaking the build 馃毃 #8

Open
greenkeeper bot opened this issue Aug 11, 2019 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

commented Aug 11, 2019

The devDependency markdown-it was updated from 9.0.1 to 9.1.0.

馃毃 View failing branch.

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

markdown-it 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
  • ci/circleci: Your tests failed on CircleCI (Details).

Commits

The new version differs by 6 commits.

  • 9e5015f 9.1.0 released
  • 5093920 Browser files rebuild
  • 39a35f4 Remove extra chars from line breaks check (match CM spec)
  • faecae0 Match CommonMark spec exactly
  • d9cb3cc Don鈥檛 recognize U+2028 as a newline character
  • 9bbefc1 Create issue templates

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 Aug 11, 2019

@issue-label-bot

This comment has been minimized.

Copy link

commented Aug 11, 2019

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

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

@issue-label-bot issue-label-bot bot added the bug label Aug 11, 2019

@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

commented Aug 11, 2019

After pinning to 9.0.1 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
Projects
None yet
0 participants
You can鈥檛 perform that action at this time.