CommonMark 0.29 #290

New Issue

claunia · 2026-01-29T14:32:53Z

claunia commented

2026-01-29 14:32:53 +00:00

Originally created by @MihaZupan on GitHub (Apr 9, 2019).

0.29 has been released, opening this issue to serve as a tracker for progress/related issues.

See

Originally created by @MihaZupan on GitHub (Apr 9, 2019). 0.29 has been released, opening this issue to serve as a tracker for progress/related issues. See - [spec](https://spec.commonmark.org/0.29/) - [changelog](https://github.com/commonmark/commonmark-spec/releases/tag/0.29) - [diff](https://spec.commonmark.org/0.29/changes.html) - [announcement post](https://talk.commonmark.org/t/ann-commonmark-0-29/3126)

claunia added the enhancement label 2026-01-29 14:32:53 +00:00

claunia closed this issue

2026-01-29 14:32:54 +00:00

claunia commented

2026-01-29 14:32:55 +00:00

@MihaZupan commented on GitHub (Apr 11, 2019):

I've implemented all of the 0.29 changes I could find on the #327 branch.

No Markdig changes needed

Allow tabs in thematic breaks
Unreferenced LinkReferenceDefinitions do not affect the output
Info string is trimmed of ~~space~~ whitespace

Changes implemented

Info strings for tilde code blocks can contain backticks and tildes
Meta html tag is no longer recognised
An empty link destination may be specified using angle brackets (AutoLink and LinkReferenceDefinition)
Setex headings with no content after a LinkReferenceDefinition are parsed as literals
Decimal numeric character references consist of up to 8 7 arabic digits
Hexadecimal numeric character references consist of up to 8 6 hexadecimal digits
Interior spaces in backtick strings are not collapsed
A backtick string is trimmed of a single front and back space if it is not a space-only string
Delimiter runs can match if lengths of both are multiples of 3
Changes to how indentation with list items is interpreted (tests 282, 283)

Breaking changes

In FencedBlockParserBase, added an additional char openingCharacter argument to InfoParserDelegate.

@xoofx I can open a separate PR and revert commits to #327 if you prefer

@MihaZupan commented on GitHub (Apr 11, 2019): I've implemented all of the 0.29 changes I could find on the #327 branch. ## No Markdig changes needed - Allow tabs in thematic breaks - Unreferenced LinkReferenceDefinitions do not affect the output - Info string is trimmed of ~~space~~ whitespace ## Changes implemented - Info strings for tilde code blocks can contain backticks and tildes - Meta html tag is no longer recognised - An empty link destination may be specified using angle brackets (AutoLink and LinkReferenceDefinition) - Setex headings with no content after a LinkReferenceDefinition are parsed as literals - Decimal numeric character references consist of up to ~~8~~ 7 arabic digits - Hexadecimal numeric character references consist of up to ~~8~~ 6 hexadecimal digits - Interior spaces in backtick strings are not collapsed - A backtick string is trimmed of a single front and back space if it is not a space-only string - Delimiter runs can match if lengths of both are multiples of 3 - Changes to how indentation with list items is interpreted ([tests 282, 283](https://spec.commonmark.org/0.29/#example-282)) ## Breaking changes - In `FencedBlockParserBase`, added an additional `char openingCharacter` argument to `InfoParserDelegate`. @xoofx I can open a separate PR and revert commits to #327 if you prefer

claunia commented

2026-01-29 14:32:56 +00:00

@xoofx commented on GitHub (May 11, 2019):

We can close this one right?

@xoofx commented on GitHub (May 11, 2019): We can close this one right?

claunia referenced this issue

2026-01-29 14:47:21 +00:00

[PR #298] [MERGED] Add Neo.Markdig.Xaml #925

Sign in to join this conversation.