This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
Update atom-linter to version 9.0.0 🚀 #50
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 9.0.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 5 commits .
See the full diff. |
|
No use of |
Arcanemagus
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 9.0.0 of atom-linter just got published.
The version 9.0.0 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 atom-linter.
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.
Commits
The new version differs by 15 commits .
aa99effPrepare v9.0.0 release1c13ce0Cleanup the changelogd2bdb3bMerge pull request #153 from steelbrain/arcanemagus/rename-rflne63ec0cRename rangeFromLineNumber to generateRange55757f9Merge pull request #152 from steelbrain/arcanemagus/xplat-clean91fb6ceUse rimraf for cross-platform clean script1c68697Merge pull request #151 from steelbrain/arcanemagus/array-range5e2fa88Return Range-compatible Array from rangeFromLineNumber1a252f2:arrow_up: Bump sb-exec to 3.1.05a92588:new: Show line number in col too big error messages8bdfa68:arrow_up: Bump sb-exec to v3.0.3693196bMerge pull request #149 from steelbrain/steelbrain/handle-enoent-properly0b70af5✅ Add specs for changed75ff07:memo: Document changes in CHANGELOGb30db86:new: Handle ENOENT properlySee the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴