ci: stabilise the lint job names and modernise the publish workflow

.github/workflows/python-publish.yml

@@ -17,7 +17,7 @@
 #     runs-on: ${{ matrix.os }}
 #     strategy:
 #       matrix:
-#         python-version: ["3.13"]
+#         python-version: ["3.14"]
 #         os: [ubuntu-latest]
 #     steps:
 #       - uses: actions/checkout@v4
@@ -35,7 +35,7 @@
 #     runs-on: ${{ matrix.os }}
 #     strategy:
 #       matrix:
-#         python-version: [ "3.12" ]
+#         python-version: [ "3.14" ]
 #         os: [ ubuntu-latest ]
 #     # Specifying a GitHub environment, # Specifying a GitHub environment, which is strongly recommended by PyPI: https://docs.pypi.org/trusted-publishers/adding-a-publisher/
 #     # you have to create an environment in your repository settings and add the environment name here

.github/workflows/pythonlint.yml

@@ -6,7 +6,11 @@ on:
   pull_request: {}
 jobs:
   lint:
-    name: Python Code Quality and Lint
+    # the name must not depend on the commands below: repositories built from this template use it as a
+    # required status check in their branch ruleset, and GitHub would otherwise append the whole command
+    # string - so renaming the package, or any edit to a lint invocation, silently makes the required
+    # check unreportable and blocks every pull request
+    name: "Python Code Quality and Lint (${{ matrix.linter-env }})"
     runs-on: ubuntu-latest
     strategy:
       matrix:

README.md

@@ -124,6 +124,10 @@ It just requires some manual adjustments/settings depending on your project:
 1. Fill out the metadata in the [`pyproject.toml`](pyproject.toml); Namely the package name and the `dependencies` list.
 2. Uncomment the lines in [`.github/workflows/python-publish.yml`](.github/workflows/python-publish.yml)
 3. Create a [new environment in your GitHub repository](https://github.com/Hochfrequenz/python_template_repository/settings/environments) and call it `release`.
+   If you restrict that environment's deployment branches, you **must** add a rule of type *Tag* matching `v*`.
+   A release event deploys from the tag (`refs/tags/v1.2.3`), not from a branch, so an environment that only
+   allows the `main` branch rejects every publish - and the job then fails having run no steps at all, which
+   gives you nothing to debug from.
 4. Set up a new trusted publisher [in your PYPI account](https://pypi.org/manage/account/publishing/).
    1. PyPI Project Name: The name which you defined in the `pyproject.toml` is the name of the project which you have to enter here.
    2. Owner: The GitHub organization name or GitHub username that owns the repository

pyproject.toml

@@ -62,9 +62,6 @@ ignore = [
     "PLR2004", # magic-value-comparison
 ]
 
-[mypy]
-truethy-bool = true
-
 [tool.mypy]
 disable_error_code = []