-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.4.41 regression: module :string_lexer is not available #468
Comments
Thank you for reporting this |
You reported this very nicely, I can see the stupid misstake I made, just that I am on leave and cannot really investigate why the tests did not check this. |
Not fixed in 1.4.42 on Elixir 1.15.5 (compiled with Erlang/OTP 26) I'm afraid |
Thank you. It may be worth yanking 1.4.41/42 from Hex? |
Completely agree, however can this still be done? |
Yes, it's possible to retire a specific version |
Ty for your reply, I have looked at the So I get cold feet, honestly. But thank you for your time. |
I'll be a little bit more precise, I quote the doc
Great so far
I beg you pardon 😨 I will test with a dummy package when I have some time; probably not soon, sorry |
Yeah, I found it confusing too. |
Here's an example though: Timex 3.6.2 |
During one of the recent Thinking Elixir podcast it was mentioned that it can be done by asking Hex maintainers, but they have a policy limiting it to 48h after release if I'm not mistaken. |
Is that not for overwriting the same version, which also can be done during 1h IIRC with the CLI. Maybe this is one of the areas where documentation could be improved. |
Well are we sure there was ever a version 3.7.10 ? I have occasonally skipped patch version numbers. Ty all for your participation, but I'll just test with a dummy package. ;) |
Action : Retire versions 1.4.4[12] if savely possible. |
DONE |
Ty all for your help |
Thank you 👍🏻 |
With v1.4.41, I get
I'm sorry I don't have a quick reproduction case, as I'm calling Earmark as a LiveView component and haven't isolated this issue out yet. Given the size/scope of the v1.4.41 merge that still not on master, figured I would give a heads up if this makes sense to someone in the know.
Other things I tried:
Version info:
The text was updated successfully, but these errors were encountered: