Argh.
We had an issue with tags yesterday when launching the v2.3.0-rc.1 release, as Matt noted on twitter:
Github has strange behaviour when it comes to forks and tags (a contributor made a fork and tagged their own v2.2.2 for themselves. See the twitter thread from @theJeztah that explains exactly why that happens.
Apparently our CI still ran on the bad 2.2.2 tag and pushed it to gemfury. It shouldn’t have.
I deleted that version from Gemfury now.
@giffengrabber, thanks for that command, please run apt install caddy=2.2.1 to downgrade to the latest stable version for now.
We’ll release v2.3.0 quite soon, you can download the .deb directly from Github for now if you want to try the release candidate early (any early testing is much appreciated, it helps make sure our stable releases go without a hitch!)