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 eslint-plugin-markdown is breaking the build 🚨 #32

Open
greenkeeper bot opened this issue Oct 27, 2018 · 3 comments
Open

Comments

@greenkeeper
Copy link

greenkeeper bot commented Oct 27, 2018

The devDependency eslint-plugin-markdown was updated from 1.0.0-beta.8 to 1.0.0-rc.0.

🚨 View failing branch.

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

eslint-plugin-markdown 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 is in progress (Details).
  • bundlesize: ./src/index.js: 382B > maxSize 252B (gzip) (Details).

Release Notes for v1.0.0-rc.0
Commits

The new version differs by 12 commits.

  • f9258b7 1.0.0-rc.0
  • 8bc7c0c Build: changelog update for 1.0.0-rc.0
  • 8fe9a0e New: Enable autofix with --fix (fixes #58) (#97)
  • a5d0cce Fix: Ignore anything after space in code fence's language (fixes #98) (#99)
  • 6fd340d Upgrade: [email protected] (#100)
  • dff8e9c Fix: Emit correct endLine numbers (#88)
  • 83f00d0 Docs: Suggest disabling strict in .md files (fixes #94) (#95)
  • 3b4ff95 Build: Test against Node v10 (#96)
  • 6777977 Breaking: required node version 6+ (#89)
  • 5582fce Docs: Updating CLA link (#93)
  • 24070e6 Build: Upgrade to [email protected] (#92)
  • 6cfd1f0 Docs: Add unicode-bom to list of unsatisfiable rules (#91)

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
Author

greenkeeper bot commented Oct 27, 2018

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

@greenkeeper
Copy link
Author

greenkeeper bot commented Jan 2, 2019

Your tests are still failing with this version. Compare changes

Release Notes for v1.0.0
  • 2a8482e Fix: overrides general docs and Atom linter-eslint tips (fixes #109) (#111) (Brett Zamir)
Commits

The new version differs by 6 commits.

  • a248c9a 1.0.0
  • 902d0f7 Build: changelog update for 1.0.0
  • 2a8482e Fix: overrides general docs and Atom linter-eslint tips (fixes #109) (#111)
  • 4a5fd82 1.0.0-rc.1
  • 3920041 Build: changelog update for 1.0.0-rc.1
  • a2f4492 Fix: Allowing eslint-plugin-prettier to work (fixes #101) (#107)

See the full diff

@greenkeeper
Copy link
Author

greenkeeper bot commented Feb 24, 2020

Your tests are still failing with this version. Compare changes

Release Notes for v1.0.2
  • 52e0984 Upgrade: Update devDeps and change istanbul -> nyc (#130) (Brett Zamir)
  • d52988f Chore: Remove call to lint absent Makefile.js (#129) (Brett Zamir)
  • 5640ea6 Fix: Apply base indent to multiple line breaks (fixes #127) (#128) (Brett Zamir)
Commits

The new version differs by 13 commits.

  • 66b565b 1.0.2
  • caf733a Build: changelog update for 1.0.2
  • 52e0984 Upgrade: Update devDeps and change istanbul -> nyc (#130)
  • d52988f Chore: Remove call to lint absent Makefile.js (#129)
  • 5640ea6 Fix: Apply base indent to multiple line breaks (fixes #127) (#128)
  • 2d306ba 1.0.1
  • 7b6f11b Build: changelog update for 1.0.1
  • fb0b5a3 Fix: Indent multiline fixes (fixes #120) (#124)
  • 07c9017 Chore: Use GitHub Actions (#123)
  • b5bf014 Chore: Add Node 12 to Travis (#122)
  • dc90961 Fix: Support autofix at the very start of blocks (fixes #117) (#119)
  • 2de2490 Docs: Syntax highlight Markdown (#116)
  • fdacf0c Chore: Upgrade to [email protected] (#110)

See the full diff

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

No branches or pull requests

0 participants