Cut a patch release :)

[juanitorduz]

Feature Summary

It would be great to cut a patch release :)

Why is this needed?

I wanna make sure I have the fix in #2024 for production models (installing from git is an option, but risky)

[fehiepsi]

Hi @juanitorduz, let's address the issues in https://github.com/pyro-ppl/numpyro/issues?q=is%3Aissue%20state%3Aopen%20milestone%3A0.19 for a new 0.19 release instead of a patch release. Does that work? I can take a pass over some of them later this week. Not sure about #2036 - @Qazalbash do you need any help on it?

[juanitorduz]

Sure! Makes sense! I'll also see what I can do on those issues :)

[Qazalbash]

Hi, regarding #2036 — I’ve addressed most of the errors, and there are around 400 remaining. Apologies, but I’m currently tied up with other commitments until next week. I’m happy to push the current changes if someone would like to pick it up from there, or I can continue once I’m available again. Let me know what works best!

[fehiepsi]

I think we can merge the fixes and make several follow-up PRs. I can make a list of remaining pieces so that we can split the work.

[Qazalbash]

Sure I will push them!

Please see, #2050.

[Zethson]

May I very politely request to also add #2051 to the milestone of this release?

[juanitorduz]

Thank you very much, folks 💪 !