Release v4.2.1 #261
Merged
Release v4.2.1 #261
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
Hopefully this will address slevithan#259 Here's the previous release PR, for reference: slevithan#223 Not exactly sure where all the `package-lock.json` changes came from, but I'm guessing it's due to a newer `npm` version (I'm on `v6.5.0`).
|
Thanks, @josephfrazier! Tagged. Also published v4.2.2 on npm with a minor adjustment to comment out some failing tests. |
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.
Suggestion cannot be applied right now. Please check back later.
Hopefully this will address #259
Here's the previous release PR, for reference:
#223
Not exactly sure where all the
package-lock.jsonchanges came from,but I'm guessing it's due to a newer
npmversion (I'm onv6.5.0).