update to cmark-gfm 0.29.0.gfm.0 #98
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
|
Build failure looks to be Rubocop configuration related. |
|
😎 Thanks! |
|
FYI, commonmarker 0.20.0 is now live on github.com. |
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.
cmark 0.29.0 has been released (as has the same version of the spec, though the spec website hasn't updated yet) -- I've published cmark-gfm 0.29.0.gfm.0 just now which just pulls in changes made since then, and here's the commonmarker change.
(Maybe worth noting: cmark-gfm's change to safe-by-default/unsafe-via-option was taken up in upstream cmark!)