We release packages and upload them to PyPI (wheels and source tarballs).
The following scripts are used in the process:
We use git tags to identify releases, using Semantic Versioning. For
Since version 1.21.0, our packages are cryptographically signed by one of four PGP keys:
These keys can be found on major key servers and at https://dl.eff.org/certbot.pub.
Releases before 1.21.0 were signed by the PGP key
A2CFB51FA275A7286234E7B24D17C995CD9775F2 which can still be found on major
Notes for package maintainers¶
Please use our tagged releases, not
Do not package
certbot-compatibility-testas it’s only used internally.
To run tests on our packages, you should use pytest by running the command
python -m pytest. Running
pytestdirectly may not work because PYTHONPATH is not handled the same way and local modules may not be found by the test runner.
If you’d like to include automated renewal in your package:
certbot renew -qshould be added to crontab or systemd timer.
A random per-machine time offset should be included to avoid having a large number of your clients hit Let’s Encrypt’s servers simultaneously.
--preconfigured-renewalshould be included on the CLI or in
cli.inifor all invocations of Certbot, so that it can adjust its interactive output regarding automated renewal (Certbot >= 1.9.0).
jwsis an internal script for
acmemodule and it doesn’t have to be packaged - it’s mostly for debugging: you can use it as
echo foo | jws sign | jws verify.
Do get in touch with us. We are happy to make any changes that will make packaging easier. If you need to apply some patches don’t do it downstream - make a PR here.