I just pushed a few commits implementing POST-as-GET and removing the old API v1 compatibility. Would be great to have some feedback on the changes. If there are no issues this will be released as 0.6.3 or maybe even 0.7.0 (removing API v1 might be a good reason for the latter).

ACME v1 removal has been reverted as I was told that there actually are CAs out there implementing (only) the v1 protocol. I'll keep it around as long as it doesn't become a major inconvenience (e.g. on bigger code changes).

Sorry for the release confusion over the last two days... I had to rush a time critical release and messed up a few things... With 0.6.5 everything should be fine now...

To make it official: dehydrated will move, the license will NOT change, and I will still take care of the project. I was approached by APILayer, they wanted to buy the project and will pay me for maintaining it. You can find more details on lukas.im/2020/01/30/sel…

Thinking about releasing a new version in the next few days. If you're (still) experiencing any major issues with the current master branch please open or comment on the corresponding ticket.

Version 0.7.0 has been released! 🥳🎉🍾🚀

I just released dehydrated v0.6.0. Have fun, but don't be too wild(card)!

This dehydrated release includes mainly support for the upcoming ACME v2 endpoint (including support for wildcard certificates), a new hook for external CSR generation/fetching and a few more minor fixes and changes here and there (see changelog and git log for more details).

Aaand I released dehydrated 0.6.1, now using the new public Let's Encrypt ACMEv2 endpoint by default :)

Donations have been really generous over the last few days. For me this gives working on dehydrated a completely new feeling, I'm not only working on something that a lot of people use, but something that people actually love using :) Thank you all!

I just released dehydrated 0.6.2. This release is mostly a bugfix release, but there are some new features as well. Have a look at the changelog for more details.