You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(README): fix wording; also trigger version bump after dep bumps
Automated ependency bumps for security in #264, #265, and #266 will not trigger a semver release.
I'm using this wording tweak in README to handle this.
Copy file name to clipboardExpand all lines: README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@
25
25
26
26
## Node
27
27
28
-
We pin mastarm to a specific version of node due to inconsistencies across installation and building when using multiple versions. *Node 8 is now required to run mastarm*.
28
+
We pin mastarm to a specific version of node due to inconsistencies across installation and building when using multiple versions. *Node 8 is now required to run mastarm*.
29
29
30
30
## Install
31
31
@@ -240,7 +240,8 @@ also pass in an arbitrary number of paths to directories or files to lint.
240
240
241
241
`lint-messages` is somewhat opinionated about how messages should be used in code. They should be imported
242
242
from a local module called `messages`, and referred to using dot notation. It will work regardless
243
-
of whether you import the top-level messages object or named children; the following all work:
243
+
of whether you import the top-level messages object or named children. The following import strategies
0 commit comments