v7.6.0

[sirosen]

2026-07-13

Features

• The --help output for pip-compile and pip-sync commands has been extended to include usage examples -- by @Dzhud.

  PRs and issues: Add examples of usage to --help command #1142

• Added --uploaded-prior-to as a passthrough option for pip-compile, allowing users to restrict package candidates to versions uploaded before a given datetime. Requires pip >= 26.0 -- by @miettal.

  PRs and issues: Consider a setting for delaying dependency updates #2288

• pip-tools is now compatible with pip 26.1 -- @gaborbernat.

  PRs and issues: Fix incompatibilities with pip v26.1 #2379

Improved documentation

• Fixed the contents sidebar for the index doc -- by @sirosen.

  PRs and issues: Add a TOC to the README #2169

• pip-tools now has a policy regarding LLM-generated contributions, noted in the contributing documentation -- by @sirosen.

  Thanks to @0cjs, @gpshead, mr-@c, @samdoran, @webknjaz, and everyone else in the broader community who helped us to craft a policy which is considerate of contributors and protective of the project and its maintainers.

  PRs and issues: Introduce an initial LLM Usage Policy #2318

• pip-tools' documentation now features a section titled "Reference" covering the CLI commands and configuration. Configuration documentation has been removed from the readme.

  -- by @sirosen

Contributor-facing changes

• CI testing now runs on Intel and ARM macOS runners, and is pinned to a specific macOS version -- by @sirosen.

  PRs and issues: [TODO][CI] Add macOS 14 ARM 64 to the matrix #2079, feat: Add macOS 14 ARM 64 runners to the matrix #2132, Use macos-26 runners and test on Intel/ARM #2348

• pip-tools now has a policy regarding LLM-generated contributions, noted in the contributing documentation -- by @sirosen.

  Thanks to @0cjs, @gpshead, mr-@c, @samdoran, @webknjaz, and everyone else in the broader community who helped us to craft a policy which is considerate of contributors and protective of the project and its maintainers.

  PRs and issues: [policy] Good-faith agentic contributions and LLM use, and avoiding death by a thousand AI slops #2278, Introduce an initial LLM Usage Policy #2318

• Started running {pypi}zizmor as a part of CI pipelines to improve security of how we configure GitHub Actions CI/CD -- by @webknjaz.

  PRs and issues: 🧪 Integrate Zizmor checks into GHA CI/CD #2327

• pip-tools docs now support GitHub Flavored Markdown admonition blocks -- by @webknjaz.

  PRs and issues: 📝💅 Re-integrate GFM admonitions via click_extra.sphinx ext #2343

• Coverage reporting in pip-tools now skips _t.TYPE_CHECKING blocks -- by @gaborbernat.

  PRs and issues: Recognize the project's _t typing alias in coverage config #2386

• piptools.repositories.LocalRequirementsRepository now accepts any piptools.repositories.BaseRepository subclass as its proxied repository, not only piptools.repositories.PyPIRepository -- by @gaborbernat.

  PRs and issues: ♻️ refactor(local): accept any BaseRepository as the proxied repo #2387

• A handful of f-string conversions in piptools.utils and the CLI entry points in piptools.scripts.compile and piptools.scripts.sync carried a stray space before !s (e.g. f"...{value !s}..."). PEP 498 forbids the whitespace before the conversion flag and tooling differs on whether the form parses; the literals are now in canonical {value!s} shape -- by @gaborbernat.

  PRs and issues: Drop stray whitespace before !s in f-string conversion flags #2388

• A session-scoped autouse fixture in tests/conftest.py now drops every PIP_* environment variable before any other fixture runs, so the test suite no longer flakes on contributor machines whose shell exports PIP_INDEX_URL, PIP_FIND_LINKS, PIP_TRUSTED_HOST, and the rest of the family for a corporate mirror. Tests that need a specific variable keep their function-scoped pytest:pytest.MonkeyPatch.setenv and supersede the session-level deletion -- by @gaborbernat.

  PRs and issues: Neutralize PIP_* environment variables in the runner fixture #2390

• The Sphinx configuration now resolves cross-references for packaging, pip, click, build, and importlib_metadata via intersphinx, and the deprecated sphinx.util.console.bold helper is replaced with a plain logger.info call (the colour markup never rendered in CI logs anyway). Cross-references in docstrings that previously fell back to nitpick suppression now link to the upstream documentation -- by @gaborbernat.

  PRs and issues: Add intersphinx mappings for packaging, pip, click, build, importlib_metadata #2391

• The Notify Codecov CI workflow job now only fails on privilege errors in the upstream project repository runs. This fixes a problem contributors face when running CI within their forks that are not filed as true Codecov-side projects.

  -- by @gaborbernat and @webknjaz

  PRs and issues: Let CI completion Codecov notify vote upstream #2392

• Fixed incorrect nitpick ignore regexes -- by @sirosen.

• pip-tools CI now pins GitHub Actions versions to hashes -- by @sirosen.

• pip-tools now tests against PyPy 3.11 -- by @sirosen and @webknjaz.

• pip-tools's GitHub Actions config now specifies the Ubuntu and Windows runner versions used.

---

This discussion was created from the release v7.6.0.