This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
Update atom-linter to version 6.0.0 🚀 #38
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
|
This codebase doesn't currently use |
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.
Hello lovely humans,
atom-linter just published its new version 6.0.0.
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 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.
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!
🌴
GitHub Release
rangeFromLineNumberto return a range that wraps a word not an entire line. (API breaking change)The new version differs by 39 commits .
f9fb44d:arrow_up: Bump version to 6.0.059fbd08:memo: Document change in CHANGELOG74ac911Merge pull request #136 from steelbrain/steelbrain/highlight-next-chunk-onlye888b37:art: Address reviewer's comments890f080:white_check_mark: Update specs to match latest behaviorba06841:new: Add a smart colStart if one is not already provided3f6510f:new: Determine word regexp based on position56f95b1:new: Properly clip the range in rangeFromLineNumber4fdae4f:arrow_up: Bump version to 5.0.243b7ee6:arrow_up: Bump version to 5.0.2f1a65ad:arrow_up: Bump sb-exec version6a8f9a1:arrow_up: Bump version to 5.0.1387d335:memo: Document change in changelog35978b2:arrow_up: Bump sb-exec versionba2ed9d:bug: Fix URLs in package.jsonThere are 39 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade