Skip to content

v10.0.1

Latest
Compare
Choose a tag to compare
@github-actions github-actions released this 22 Apr 15:22
· 73 commits to main since this release

📝 Release notes

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

🌱 v10.0.1 is marked as a stable release.

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

v10.0.1

(2024-04-22)

Bug fixes

  • Fixed a flaw where internally unhandled exceptions could crash the
    worker threads and eventually starve the server of its processing
    resources. It is no longer and issue and the unhandled errors are
    now logged and suppressed except for a few expected exceptions that
    are used for normal interruption requests.

    -- by @cameronbrunner and @webknjaz

    Related issues and pull requests on GitHub: #310, #346, #354,
    #358, #365, #375, #599, #641, #649.

  • Fixed compatibility with Python 3.8 in the built-in TLS adapter that
    relies on :pypython:ssl.

    Modern Python versions communicate specialized exceptions
    :pyssl.SSLEOFError and :pyssl.SSLZeroReturnError where the older
    versions errored out in a very generic way.

    -- by @toppk and @webknjaz

    Related issues and pull requests on GitHub: #517, #518.

Packaging updates and notes for downstreams

  • Started signing the package distribution artifacts in CI/CD with
    Sigstore and uploading them to GitHub Releases -- by @webknjaz.

    Related commits on GitHub:
    27a3c944,
    c45f184e.

  • The changelog management is now implemented through the
    :stdTowncrier <towncrier:index> tool -- by @webknjaz.

    The contributors are now expected to :stdinclude change log fragment files in their pull requests <adding change notes with your prs>.

    These news snippets can link one or more issues or pull requests,
    and be of one or more of the following categories:

    • bugfix: A bug fix for something we deemed an improper
      undesired behavior that got corrected in the release to match
      pre-agreed expectations.
    • feature: A new behavior, public APIs. That sort of stuff.
    • deprecation: A declaration of future API removals and breaking
      changes in behavior.
    • breaking: When something public gets removed in a breaking
      way. Could be deprecated in an earlier release.
    • doc: Notable updates to the documentation structure or build
      process.
    • packaging: Notes for downstreams about unobvious side effects
      and tooling. Changes in the test invocation considerations and
      runtime assumptions.
    • contrib: Stuff that affects the contributor experience. e.g.
      Running tests, building the docs, setting up the development
      environment.
    • misc: Changes that are hard to assign to any of the above
      categories.

    Related issues and pull requests on GitHub: #654.

Contributor-facing changes

  • Started type-checking the project with MyPy against a range of
    versions instead of just one — Python 3.8–3.12 -- by @webknjaz.

    Related commits on GitHub:
    4fa1e663,
    676edc4e,
    be9dbc41.

  • The project how has a .git-blame-ignore-revs letting GitHub know
    which auto-formatting revisions to ignore. It is also possible to
    integrate it locally, if one wants to do so.

    -- by @webknjaz

    Related commits on GitHub:
    5980a3fb,
    f8a1cc4d.

  • The project adopted the autopep8 tool to assist with automatic
    code formatting. It is chosen over black because it is less
    intrusive which is important to the maintainer as it promotes
    inclusivity. autopep8 is integrated into the pre-commit check
    runner and is configured to only correct 8 violations, avoiding
    changes to compliant snippets.

    -- by @webknjaz

    Related commits on GitHub:
    65ba7e69.

  • The continuous integration and pull request merges have been set up
    to only merge pull requests through merge queues -- by @webknjaz.

    Related commits on GitHub:
    a7149e0c.

  • Documented the upgraded :stdrelease process <contributing/release_guide> -- by @webknjaz.

    Related commits on GitHub:
    df0d1a08.

  • The changelog management is now implemented through the
    :stdTowncrier <towncrier:index> tool -- by @webknjaz.

    The contributors are now expected to :stdinclude change log fragment files in their pull requests <adding change notes with your prs>.

    These news snippets can link one or more issues or pull requests,
    and be of one or more of the following categories:

    • bugfix: A bug fix for something we deemed an improper
      undesired behavior that got corrected in the release to match
      pre-agreed expectations.
    • feature: A new behavior, public APIs. That sort of stuff.
    • deprecation: A declaration of future API removals and breaking
      changes in behavior.
    • breaking: When something public gets removed in a breaking
      way. Could be deprecated in an earlier release.
    • doc: Notable updates to the documentation structure or build
      process.
    • packaging: Notes for downstreams about unobvious side effects
      and tooling. Changes in the test invocation considerations and
      runtime assumptions.
    • contrib: Stuff that affects the contributor experience. e.g.
      Running tests, building the docs, setting up the development
      environment.
    • misc: Changes that are hard to assign to any of the above
      categories.

    Related issues and pull requests on GitHub: #654.