Currently, there is a test failing that has been skipped (crates/footnote/tests/fixtures/_7.md), but should eventually be fixed, for dealing with code blocks starting on the first line of a footnote definition.

This is quite a niche use case, and I couldn't easily work out how to fix, so left here for later 😅 .

Currently, cargo release minor will dry-run through and update all packages to a new version,
but then warn e.g. updating xxx to 0.2.0 despite no changes made since tag xxx-v0.1.0.
Then you can decide which packages to release individually, and what type of version bump (major/minor/patch)

Ideally, there would be one command that

1. would not release unchanged packages (unless there were changes to dependent packages)
2. Could independently decide which version bump type, per package

As a meta package to enable all CommonMark, plus all GFM extensions: https://github.github.com/gfm/

• Extension not yet created: https://github.github.com/gfm/#disallowed-raw-html-extension-
• Should heading anchors be included (optional feature?)

e.g. [email protected]

Currently, they are matched by back-scanning from @, if the previous sibling is a Text node.
But this does not work with emphasis, which already matches against the _

GFM now allows for markup such as :

https://github.com/orgs/community/discussions/16925

It is not the same format used by the containers plugin : https://mdit-plugins.github.io/container.html

It will not be supported by markdown-it native : markdown-it/markdown-it#974

and maybe make textify pluggable