Open
Conversation
|
hey @rpl, any chance that this could be finished ? :-) I was thinking that if you'd release this as 2.2.1 or 2.3.0 instead of 3.0.0 like you did, we could update our |
|
@rpl : Another bump if you are planning to update? |
This file contains hidden or 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.Suggestion cannot be applied right now. Please check back later.
This PR includes a set of changes to update the svgo dependency to v.2.6.0 along with updating the fork to the tip of the upstream main branch (and keeping the diff between this fork and the upstream version as small and clean as possible).
This is meant to cover and supersede #1
TODO:
npm audit)