• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

trungdong / prov / 31246341818
98%

Build:
DEFAULT BRANCH: master
Ran 08 Aug 2026 07:31AM UTC
Jobs 6
Files 18
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

08 Aug 2026 07:31AM UTC coverage: 97.795%. Remained the same
31246341818

push

github

web-flow
Add a release runbook (#369)

* Add a release runbook

Until now the release process lived only inside per-release plan documents, so each release meant re-deriving it from the last one, and the hard-won details were never written down anywhere a contributor would look. This captures the sequence as executed for 3.1.0: pre-flight matrix and build checks, what to stamp, how the Codacy and Coveralls gates differ, the TestPyPI dry run, and the verification that catches a wheel missing its package data.

It records three things that are not discoverable from the workflow file: that creating the GitHub release is what publishes to PyPI, that workflow_dispatch can only ever reach TestPyPI, and that a conda-forge merge failing with "the base branch policy prohibits the merge" actually means the gh token lacks the workflow scope.

* Open the 2.x line to back-ported bug fixes through 2.6.0

Since 3.0.0 shipped, the 2.x maintenance line has been documented as receiving security fixes only. A review of everything merged after the 2.5.1 tag found a substantial set of conformance and correctness fixes that port cleanly to 2.x, so the line is opened to back-ported bug fixes as well.

The widening is bounded by scope rather than by date: 2.x accepts back-ported fixes up to and including 2.6.0, then reverts to security fixes only. New features and behaviour-breaking corrections are never back-ported and stay on 3.x, which keeps the commitment from reading as open-ended.

See docs/superpowers/specs/2026-08-07-2x-backport-programme.md for which fixes are in scope, how they are staged across 2.5.2, 2.5.3 and 2.6.0, and which are deliberately left unported.

* Specify the 2.x back-port programme

Assesses every fix merged into master after the 2.5.1 tag for portability to the 2.x maintenance line, and stages the portable ones across three releases: 2.5.2 (the XXE hardening, shippable under the existing security-only policy), 2.5.3 (fixes that correct broken behaviour wit... (continued)

494 of 495 branches covered (99.8%)

2794 of 2857 relevant lines covered (97.79%)

5.87 hits per line

Jobs
ID Job ID Ran Files Coverage
1 Python3.11 - 31246341818.1 08 Aug 2026 07:32AM UTC 18
97.79
GitHub Action Run
2 Python3.10 - 31246341818.2 08 Aug 2026 07:32AM UTC 18
97.79
GitHub Action Run
3 Python3.13 - 31246341818.3 08 Aug 2026 07:32AM UTC 18
97.79
GitHub Action Run
4 Python3.14 - 31246341818.4 08 Aug 2026 07:31AM UTC 18
97.79
GitHub Action Run
5 Pythonpypy3.11 - 31246341818.5 08 Aug 2026 07:34AM UTC 18
97.79
GitHub Action Run
6 Python3.12 - 31246341818.6 08 Aug 2026 07:32AM UTC 18
97.79
GitHub Action Run
Source Files on build 31246341818
  • Tree
  • List 18
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #31246341818
  • 9917bd4b on github
  • Prev Build on master (#31224073796)
  • Next Build on master (#31246958411)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc