I have just released
Earmark 1.4.47 2024-07-12
First a small explanation
This has been backported from Fixes #154 by RobertDober · Pull Request #156 · RobertDober/earmark_parser · GitHub.
It seems however important to clarify some things concerning the split between Earmark and EarmarkParser which
were confusing.
They are only historically related and there is no formal dependency anymore. As I am still happy to help out with Earmark but alsovery relieved not to be obliged I might as well continue to do backports and bugfixes (but probably not new features). Howeverall decision about what will happen with Earmark and how the internal parser evolves will not be taken by me.
This release is done beacause our new maintainer asked me to make it so (couldn’t resist this one) and because he accepted the PR for the backport.
Unfortunately the naming of the projects and the internal module Earmark.Parser have made people unconfortable with bug reports.
Please note two things here.
Firstly, and most importantly, nowbody will be harsh or impolite of you file an issue in the wrong project, we’ll figure it out.
Secondly I have opened an Issue about better documenting this in both projects.
All comments and ideas on this topic are very much welcome.
Hopefully this will become much clearer soon.
And now for something completely different
-
Fix for #361
Kudos to bradhanks
Much work was put into Earmark by Brad in the last months working on getting rid of warnings, typespecs and mix format compliance, the details of which are not
really interesting in RNs, but shall be duely appreciated.
