ci: add coverage gate and benchmark job, bump action pins - #6
Open
lbliii wants to merge 1 commit into
Open
Conversation
- Enforce coverage floor via [tool.coverage.report] fail_under = 79 (honest ratchet toward 80; measured 79.30% on 2026-07-08). The existing test job's --cov run now fails below the floor via pytest-cov. - Add a non-gating benchmarks CI job: runs the pytest-benchmark suite (benchmark_vs_pygments.py, incl. Pygments comparison) and the parallel scaling script, uploading benchmark-results.json as an artifact. Baseline comparison is deferred to the evidence epic. - Bump action pins to ecosystem current (matching lbliii/kida): checkout v4->v7, setup-uv v4->v7, cache v4->v6, setup-python v5->v6, upload-artifact v4->v7, download-artifact v4->v8, upload-pages-artifact v3->v5, deploy-pages v4->v5. Part of #5 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements three tasks of #5 (hygiene baseline alignment): a coverage gate, a CI benchmark job, and current action pins.
Coverage gate
[tool.coverage.report] fail_under = 79topyproject.tomlas an honest ratchet toward 80. pytest-cov picks this up from the existing--covinvocation in the test job — verified locally:Required test coverage of 79.0% reached. Total coverage: 79.30%.Benchmark job (non-gating)
New
benchmarksjob intests.yml:pytest-benchmark+pygmentsat the job level (kept out of the dev group / lockfile since they're only needed here).uv run --no-sync pytest benchmarks/benchmark_vs_pygments.py --benchmark-only --benchmark-json=benchmark-results.json(the file must be passed explicitly —python_files = ["test_*.py"]excludesbenchmark_*.pyfrom directory collection). 17 benchmarks incl. the Pygments comparison and the slow 10k-line cases; ~22s locally.benchmarks/benchmark_parallel.pyfor free-threading scaling numbers.benchmark-results.jsonas an artifact. No baseline comparison yet — that's the evidence epic (Epic: Evidence — prove the ReDoS-safety and speed claims (P1) #4).Action pins
Bumped to ecosystem current (matching lbliii/kida) across all four workflows:
pypa/gh-action-pypi-publish@release/v1left as-is (floating release branch).Verification
Part of #5
🤖 Generated with Claude Code