Update remark to version 5.0.1 🚀 #73
Conversation
33016ec
to
d43cb40
Compare
|
Well this is interesting, it seems to be failing because |
|
Yup, I externalised the CLI! So now |
|
It should only be a |
|
No, we’re using the Now I think of it, just updating won’t work either, I’ve changed quite a lot and have to see how to bring it all to linter-markdown :( I’ll try to get to it tonight / tomorrow? |
|
Looks like it doesn't like both being installed: |
|
Okay, I'll just leave it to you then, if you need any help let me know! |
|
@Arcanemagus Sorry, it has taken me longer than expected, and it’s going to take me even more time 😧 |
|
No worries, I'll get the eslint update right now, it's waiting on an update to the Atom CI script anyway. |
d43cb40
to
e1459a4
Compare
* Update remark to version 5.0.0; * Use `unified-engine-atom` to deal with processing, this adds support for `.remarkignore` files, local remark-lint configuration files. Closes GH-71 - `remark-lint` specified in `.remarkrc` or `package.json` files now precedes over the packaged `remark-lint`. Closes GH-73 - Update `remark`; Closes GH-76, closes GH-83 - Using `unified-engine`, which comes with pretty JSON errors.
* Update remark to version 5.0.0; * Use `unified-engine-atom` to deal with processing, this adds support for `.remarkignore` files, local remark-lint configuration files. Closes GH-71 - `remark-lint` specified in `.remarkrc` or `package.json` files now precedes over the packaged `remark-lint`. Closes GH-73 - Update `remark`; Closes GH-76, closes GH-83 - Using `unified-engine`, which comes with pretty JSON errors.
|
This PR is superseded by #93. |
Hello lovely humans,
remark just published its new version 5.0.1.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of remark.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgradeThis change is