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

Update markdownlint-cli to the latest version 🚀 #17

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Feb 25, 2019

The devDependency markdownlint-cli was updated from 0.13.0 to 0.14.0.

This version is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.


Release Notes for 0.14.0
  • Update markdownlint dependency to 0.12.0
  • Automatically use .markdownlint.yaml/.markdownlint.yml (as with .markdownlint.json)
  • Add Dockerfile for use with Docker
  • Allow arrays for custom rules
Commits

The new version differs by 8 commits.

  • 9d689eb Bump version 0.14.0
  • 794b4bb Add Node.js version 11 to .travis.yml.
  • c3ae338 Allow .markdownlint.yaml/.markdownlint.yml as with .markdownlint.json (fixes #50).
  • 61c8fba Upgrade 'markdownlint' dependency, add "package-lock.json" (#51)
  • ecc342a Configuration is stored in JSON, YAML or INI files (#48)
  • 8c7e07f added dockerfile (#47)
  • bb29251 Allow custom rules to export an array of custom rule objects.
  • 8eadb9f Resolve new xo violation: "The catch parameter should be named error.".

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 🌴

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

Successfully merging this pull request may close these issues.

0 participants