v11.0.0

[github-actions[bot]]

📝 Release notes

📦 PyPI page: https://pypi.org/project/cheroot/11.0.0

🌱 v11.0.0 is marked as a stable release.

🔗 This release has been produced by the following workflow run: https://github.com/cherrypy/cheroot/actions/runs/17894178348

v11.0.0

(2025-09-21)

Features

• When load is too high, Cheroot now responds with a 503 Service
  Unavailable HTTP error. Previously it silently closed the connection.

  -- by @itamarst

  Related issues and pull requests on GitHub: When connection queue is full, respond with a 503 error. #745.

Removals and backward incompatible breaking changes

• Cheroot dropped support for Python 3.6 and 3.7. It now requires Python
  3.8 or later.

  -- by @jaraco

  Related issues and pull requests on GitHub: Drop support for Python 3.7 #565, Drop support for Python 3.7 and earlier #633.

  Related commits on GitHub:
  437863ee.

Packaging updates and notes for downstreams

• Declared Python 3.12 and Python 3.13 as supported officially -- by
  @webknjaz.

  Related issues and pull requests on GitHub: 📦🧪 List Python 3.12 @ package meta & CI matrix #696.

  Related commits on GitHub:
  5db4f634.

• The minimum version of the setuptools-scm build dependency has been
  set to 7. The Git archives are now produced by it natively, instead of
  relying on a third party plugin which is no longer being used.

  -- by @serhii73

  Related issues and pull requests on GitHub: Use setuptools-scm v7+ for building the dists #628.

• The packaging metadata has been migrated to the pyproject.toml-based
  621 declaration -- by @jaraco and @webknjaz.

  As a part of this update, the minimum version of the setuptools
  build backend was bumped to 61.2. Moreover, any compatibility shims
  that existed in setup.cfg and setup.py have been removed for good.

  Related issues and pull requests on GitHub: 📝 Switch packaging metadata to use PEP 621 #690.

Contributor-facing changes

• The test infrastructure has been updated to stop using the
  pytest-forked plugin -- by @jaraco and @webknjaz.

  This plugin was causing problems with upgrading to modern versions of
  Pytest and it is not going to be fixed anytime soon.

  It was used in a test that interacts with the system resource limits
  under *NIX environments in hopes to isolate the side effects caused
  by the preparatory code.

  It is possible that this will have an effect on the test sessions and
  we may have to look for alternative solutions for test process
  isolation.

  Related issues and pull requests on GitHub: Pytest 7: test_high_number_of_file_descriptors causes next test to fail #502, test_tls_client_auth: previous item was not torn down properly #511, Tests failing when building locally (in typeguard) #680,
  Disable forked and unpin pytest #681, 🧪 Stop using pytest-forked #703.

• The test infrastructure has been updated to start using the upstream
  reusable workflow reusable-tox.yml from tox-dev/workflow -- by
  @webknjaz.

  This chance allows us to de-duplicate the commonly used CI shape.

  Related issues and pull requests on GitHub: 🧪 Use reusable-tox.yml @ tox-dev/workflow #743.

---

---

This discussion was created from the release v11.0.0.