starred/certbot-certbot-2
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-07-28 08:05:31 +02:00
Code Issues Packages Projects Releases Wiki Activity

remove 1.32.x deps

Browse Source
This commit is contained in:
Brad Warren
2023-02-09 18:42:41 -08:00
parent 3512d15dff
commit f91d3ca828
2 changed files with 2 additions and 202 deletions
Download Patch File Download Diff File Expand all files Collapse all files
certbot/docs/contributing.rst
+2 -8
View File
@@ -585,8 +585,8 @@ include our snaps, Docker images, Windows installer, CI, and our development
environments.
In most cases, the file where dependency versions are specified is
``tools/requirements.txt``. There are three exceptions to this. The first is
our "oldest" tests where ``tools/oldest_constraints.txt`` is used instead. The
``tools/requirements.txt``. There are two exceptions to this. The first is our
"oldest" tests where ``tools/oldest_constraints.txt`` is used instead. The
purpose of the "oldest" tests is to ensure Certbot continues to work with the
oldest versions of our dependencies which we claim to support. The oldest
versions of the dependencies we support should also be declared in our setup.py
@@ -598,12 +598,6 @@ leave Certbot's dependencies unpinned. The thinking behind this test is to help
us learn about breaking changes in our dependencies so that we can respond
accordingly.
The third exception is temporary and at ``tools/1.32.x/requirements.txt``.
This file is simply a copy of ``tools/requirements.txt`` from our 1.32.x branch
to help us ensure those dependencies stay reasonably well updated while we still
have Certbot 1.x snap users. Once we've moved all snap users to Certbot 2.0,
this file should be deleted.
The choices of whether Certbot's dependencies are pinned and what file is used
if they are should be automatically handled for you most of the time by
Certbot's tooling. The way it works though is ``tools/pip_install.py`` (which