Skip to content

Conversation

@cderv
Copy link
Collaborator

@cderv cderv commented Jan 21, 2026

Relates to #13925 and jgm/pandoc#11409

This is adding a bullet in release note about this pandoc breaking change.

We don't usually do breaking change, and it is not ours, so I did not do it as a new ## Breaking section, but put it under the dependency itself.

Not sure about that though.

@cwickham what is your thought on that ?

This aimed to be in the doc.

@cderv cderv linked an issue Jan 21, 2026 that may be closed by this pull request
@posit-snyk-bot
Copy link
Collaborator

posit-snyk-bot commented Jan 21, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@cderv cderv requested a review from cwickham January 21, 2026 15:48
@cderv
Copy link
Collaborator Author

cderv commented Jan 21, 2026

I see that my reported issue was fixed jgm/pandoc@d599154

so next Pandoc version will support ^[text]{.class} syntax. So maybe this is not worth adding anything ? And anyone encountering this will find the github issue about it ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

New pandoc 3.8.3 breaks '<sup>' syntax

3 participants