Markdown 3.4 compatibility #20
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
Markdown 3.4 removed backwards-compatibility layer dating back to 2018, causing troubles for the plugin. Current version is compatible with Markdown >= 3.1, which is the same version that pelican requires.
mirekdlugosz
force-pushed
the
markdown-34-compat
branch
from
bb4f7a7 to
6d39b25
Compare
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.
Changes needed to fix #19 , which prevent plugin usage on fresh environment.
Also:
Given that plugin is currently unusable in new installations, I think it does justify new release. I might try to cut it over the weekend, unless @justinmayer is first.