These are for people using Earmark and EarmarkParser. As they address a potential naming conflict concerning compiled yecc or leex file however, a version update might be useful for all users. All work was done again by José, thank you so much.
Here are the release notes:
This is because there was a nasty warning concering the usage of dialyxir
Fixed warning because of bad config of using dialxir
Kudos to Jan Pieper
I have asked for approval of a topic to post EarmarkParser release notes in the future, I will provide a link ASAP and you will find detailed Release Notes there.
I have just released
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.
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.
Is anyone in touch with the Earmark maintainers? The project seems to be abandoned.
I am considering volunteering to at least release a version with the PR to add OTP 28 support applied, and maybe some documentation improvements, but can’t really promise much more than that, so if somebody more appropriate is willing, I won’t complain. From a logistic point of view I guess the repo will need to be forked, unless someone can get hold of pragdave to change ownership.
I don’t think it’s abandoned, @RobertDober is very active. This project is in use by ex_doc and I’m using it for https://lambdapad.com so, I hope it’s not abandoned at all 
I thought there was a new maintainer but ya, looks like Robert is still quite active.
PS, are you ever going upgrade to a netherite pick-axe? 
@manuel-rubio @sodapopcan Note that I’m talking about Earmark, not EarmarkParser. The difference is explained in the post before my last one.
Check out the open PRs that have no response from the maintainers. I emailed the maintainers listed on Hex on 29 May but have not had a reply either.
Yes, I’m an Earmark user and was talking about Earmark. I naively just looked at the commit history, though. I see what you mean by the lack of attention to PRs.
I guess I’ll have a look at the PRs. I am definitely not going to refactor or redesign Earmark, that is the reason I passed the project on to Amit.
However, I’ll try to make a release which should work with 1.19 and OTP28 ASAP
If someone would like to help or replace Amit, please open an issue on Github with DMs to Amit and YHS.