Release 0.8.0

HISTORY.rst

@@ -2,7 +2,7 @@
 History
 =======
 
-0.8.0 (unreleased)
+0.8.0 (2026-09-05)
 ------------------
 
 * Relax the ``tldextract`` pin from ``==2.2.2`` to ``>=5.3`` (#32). The

docs/release.rst

@@ -24,10 +24,10 @@ Workflow name                 ``release.yml``
 Environment name              ``pypi``
 ============================  ==============================
 
-Then, in the GitHub repository settings, create an environment named ``pypi``.
-Restricting that environment to the ``master`` branch and to tags, and adding
-required reviewers, means a release cannot be published without a maintainer
-approving the deployment.
+And a GitHub environment named ``pypi``, restricted to the ``v*`` tag pattern,
+with a required reviewer. That is what makes a release wait for someone to
+approve the deployment. Create it deliberately: GitHub will otherwise conjure
+an unprotected environment the first time a workflow names a missing one.
 
 The workflow requests an OIDC token via ``permissions: id-token: write`` and
 exchanges it for a short-lived, project-scoped PyPI credential. See the

domain_utils/__init__.py

@@ -1,6 +1,6 @@
 """Top-level package for Domain Utils."""
 
 __author__ = """Sarah Bird"""
-__version__ = '0.7.1'
+__version__ = '0.8.0'
 
 from .domain_utils import *