👕 Pin linter to standard v11
#67
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of the Change
Prior to this change, this package depended on the latest version of
standard.standard12 was recently released, and it introduced changes to the linter rules. As a result, the latest commit on master passed CI when it was first pushed to this repository 3 months ago, but it fails CI now due to the changes instandard12.In atom/styleguide#70 (comment), we decided to stick with the linter rules from
standard11 for now. Therefore, this pull request updates this package to depend onstandard11.Alternate Designs
See atom/styleguide#70 (comment)
Benefits
Fixes CI.
Possible Drawbacks
See atom/styleguide#70 (comment)