fix(deps): update rust crate comrak to 0.48.0 #3003
+3
−3
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 contains the following updates:
0.47.0->0.48.0Release Notes
kivikakk/comrak (comrak)
v0.48.0Compare Source
The breaking changes are listed right at the top! Please note that AST content now represents
NULbytes (codepoint number zero) as they were in the input; these used to be translated to the lovely � character at the very beginning of the input process, presumably so the rest of the reference C parser didn't have to deal with the possibility of strings containing NUL bytes. We can do better, though, so let's! The � character is now emitted by our formatters in place ofNUL, but if you use custom or manual formatters and emit any part of the AST content directly (without usingcomrak::html::escape,context::html::escape_href, or the same-named functions onContext), you may need to do the same translation yourself.We also no longer append a newline to the end of the file where there wasn't one originally, which meant a lot of places in the parser had to adapt to their strings not necessarily containing a newline before they ended. Careful review and extensive fuzzing should have squeaked out any unexpected overruns, but consider my eyes peeled for reports regarding this. (Ew.) We've cleaned up some sourcepos calculation which depended on this behaviour in odd ways, but there may yet be more to discover which our test suite didn't catch.
Did you know November is Trans Month? I didn't! I'm guessing it's because Trans Awareness Week falls within it, and we've been having a pretty bad time of it rights-wise around the world lately!
Happy Trans Month, and if you happen to typo it as Trans Moth, we can be happy about that too! 🏳️⚧️ ᖭི༏ᖫྀ
Parser changes:
NULbytes intoU+FFFD REPLACEMENT CHARACTERin the parse stage; do it in formatters instead. (by @kivikakk in #681)NULbytes where they were present in input, preserving the difference betweenNULand literally-entered�characters.Changed APIs:
%25in hrefs where not part of a percent-encode sequence. (by @kivikakk in #687)%character alone, such that[link](%%20)would roundtrip without change. It now roundtrips to[link](%25%20).[…], and no longer turns single-byte UTF-8 characters into the Unicode codepoint numbered at the UTF-8 byte (!). (by @kivikakk in #689)New APIs:
highlightextension,==for highlights==! These render with<mark>in the HTML formatter. (by @pferreir in #672)comrak::Node<'a>as an alias forcomrak::nodes::Node<'a>. (by @kivikakk in #673)comrak::Arena<'a>as an alias fortyped_arena::Arena<comrak::nodes::AstNode<'a>>. (by @kivikakk in #675)From<(LineColumn, LineColumn)>impl forSourcepos. (by @kivikakk in #675)comrak::nodes::NodeValue::xml_node_namepublic, when you want a handy-to-access name for a node type. (by @kivikakk in #673)options.parse.leave_footnote_definitions; this option causes footnote definitions to not be relocated to the bottom of the document, and unused references not to be garbage collected, for use with custom formatters. (by @kivikakk in #673)Bug fixes:
\[x]still being eligible for tasklist inclusion despite the escaped[. (by @kivikakk in #679)Performance:
NULand not appending a virtual EOF newline; compare before and after.Build changes:
Behind the scenes:
inlines::Scanner, reducing some needless allocations. (by @kivikakk in #675)all_optionsfuzzer now fuzzes across all options, and not just with most of them switched on. (by @kivikakk in #678)New Contributors
Diff: kivikakk/comrak@v0.47.0...v0.48.0
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.