Coverage-Untergrenze 85 % in tools/.coveragerc, gegen beobachtete 87,0 % (4.7.2, schließt #10, eröffnet #51)
CI / verify (push) Successful in 57s
Release / release (push) Successful in 38s

Files changed:
- .gitea/workflows/ci.yml
- CHANGES.md
- EVALS.md
- VERSION
- tools/.coveragerc
This commit is contained in:
2026-09-04 19:19:38 +02:00
parent fe55ad2a9c
commit e00eae08e8
5 changed files with 88 additions and 19 deletions
+6 -6
View File
@@ -120,12 +120,12 @@ jobs:
# container is no longer a special environment worth a second run.
# See instructions/dev/testing-conventions.md.
#
# Coverage is reported, not enforced: there is deliberately no
# `--cov-fail-under` yet (Gitea #10). The threshold gets set in its own
# later commit, with the measured number as its justification - one
# picked before the number is either too low to bite or too high to
# survive the next honest commit, and the second kind gets lowered
# instead of earned. Config: tools/.coveragerc.
# Coverage is measured and enforced at a floor of 85% against a measured
# 87.0% - `fail_under` in tools/.coveragerc, not a flag here, so the
# number sits next to the reasoning that produced it. It was set only
# after the number had been watched across 38 runs (Gitea #10, closed).
# A red suite from this floor means coverage actually fell; the two
# points of headroom already absorb a new thin Typer wrapper.
run: |
set -eu
cd tools