+-----------------------------------------------+
|The views and thoughts below are purely my own.|
+-----------------------------------------------+

This post was written 2026-11-15

pip-tools v7.7.0

Today we released pip-tools v7.7.0!

This one is notable on a few fronts: org moves, changes to our support matrix, and a new extra.

Jazzband -> PyPA

After many years under the stewardship of Jazzband, pip-tools has moved to be part of the PyPA organization.

We will miss Jazzband, and we are indebted to the roadies and band members who sustained pip-tools for so many years. In particular, I want to thank Jannis for not only running the organization, but also for managing the migration out.

If you want to read more about the move, check out my co-maintainer, @webknjaz’s post on this topic.

CoC, Security, and Funding

With the move into PyPA, a few administrative elements of pip-tools have changed.

  1. We are now governed by the PSF’s code of conduct.
  2. Security reporting no longer flows through Jazzband – we have setup a new reporting policy and GitHub Security Advisories.
  3. We now direct sponsors to fund PyPA or to directly sponsor the pip-tools maintainers.

Same maintainers – contributors, come join us!

This is also a good opportunity to dispell some illusions about the Python Packaging Authority (PyPA).

The name is, and always has been, a joke. PyPA is a collective of developers who are interested in working on and advancing Python Packaging. There is no authority vested in the organization or its members: it’s much more of a working group with shared administration.

There is also no joint maintenance carried out by PyPA members. Moving the project does not give us access to a new contributor or maintainer pool. We’re the same folks, continuing to maintain pip-tools, and past contributors remain welcome.

Python Support, -3.9, +3.15(t)

We dropped Python 3.9 and moved our upper testing bound to Python 3.15 .

pip Support, >=26.2.2 and the stable extra

We have made some rather dramatic changes to our support matrix with respect to pip versions!

For a long time, I have wanted to move up our lower bound. This impacts testing, type checking, and our overall support burden. Plus, using newer pip verisons unlocks some internal features.

As of v7.7.0 , we no longer support older pip versions, prior to 26.2.2 .

Older versions of pip bundle root certificates which are now considered unsafe, and we debated where and how to move our lower bounds based on (or not based on!) this knowledge. As maintainers, we discussed whether or not this is a change that helps secure user systems, and our conclusion is that we cannot say it does.

If you are installing pip-tools into an environment with an older pip version, whatever tool used to install the new pip-tools and new requisite pip versions must itself be secure. It is out of scope for package metadata to speak to the security of the environment which processes it – we simply cannot say whether or not the new version will be installed securely or not.

However, there are two notable benefits to having this newer lower bound:

  1. If you securely install the update, you are guaranteed not to have a known-insecure pip version after that point.
  2. For pip-tools contributors, we no longer expose developers to the risk of installing and using older pip versions for testing.

Installing with pip-tools[stable]

As a new feature in this release, pip-tools provides an extra (optional dependency declaration) named stable. The stable extra applies an upper bound to the included pip version, capping it at the latest version which was tested in pip-tools CI at the time of release.

Most users should not need to use stable, but it’s an excellent utility when releases of pip cause breakage. If you want to pin back the version of pip in a pinch, try using pip-tools[stable].

Bugfix: PyPI JSON API URL

We have some minor bugfixes in this release, but one is particularly impactful.

In v7.6.1, we introuced a bug in how we constructed PyPI JSON API URLs. As a result, pip-tools on affected versions does not properly call the PyPI JSON API for metadata, and in many cases will be slower and will use more network and disk than it should.

Updating to v7.7.0 fixes the bug, and should guarantee a fast execution path on index servers like PyPI which offer the PyPI JSON API.

Retrospective

This release has been a long time coming. We’ve been working on it on and off as time allows, and it’s taken weeks of sporadic efforts to make it happen.

As volunteers, it’s often hard for us to coordinate – there’s no fixed time in our schedules for this work, and we do it as we’re able. Any of a number of non-online responsibilities (healthcare needs, work, caretaking, etc) can easily disrupt us and make it hard to move volunteer projects forward. But we make it happen.

I continue to find it a privilege to be able to work with such excellent people, and to call them my colleagues and friends.