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

zostera / django-bootstrap5 / 38129323950
100%

Build:
DEFAULT BRANCH: main
Ran 11 Oct 2026 09:43AM UTC
Jobs 1
Files 16
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

11 Oct 2026 09:42AM UTC coverage: 100.0%. Remained the same
38129323950

push

github

web-flow
Sync the release preflight from django-marina (#896)

* Sync the release preflight from django-marina

Propagation of zostera/django-marina#694, where the reasoning lives.

just release-check listed only commits touching src/, then closed with "Every
commit above must be covered by an entry", which reads as a complete list and
is not one. Anything tooling-only was invisible to it. It now prints a second
group for commits touching nothing in src/, under a heading that says to read
them rather than a rule, because no rule fits: a Dependabot bump of a dev
dependency is nothing to a user, while a lint rule or a contributor policy
belongs in the notes.

just build now fails when uv.lock does not name the version in pyproject.toml,
and just relock regenerates the lock without upgrading anything. uv sync
--frozen does not check the project's own version, so a stale lock previously
passed twine, check-manifest, pyroma and both smoke tests unnoticed. That is
not theoretical: it is how a version bump shipped here with the previous
version still in the lock.

MAINTAINING.md release steps 1 and 2 updated to match. The justfile is
byte-identical to django-marina again.

Verified: just lint, just build and just test-cov at 100%. just relock was a
no-op, so this lock was already current.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* Say what release-check reports straight after a cut

Propagation of zostera/django-marina#696.

In the window between merging the release PR and pushing the tag, just
release-check prints "(none)" for the Unreleased entries next to every commit
since the previous tag. Stamping the section removes the heading the recipe
looks for, and the tag it compares against is still the old one. Correct, and
it reads as if the changelog has been lost.

Raised by the django-bootstrap4 session, which hit it while cutting 26.3. It
does not show up in django-marina, where the tag sits on HEAD so both lists
come back empty and the... (continued)

216 of 216 branches covered (100.0%)

Branch coverage included in aggregate %.

705 of 705 relevant lines covered (100.0%)

15.0 hits per line

Jobs
ID Job ID Ran Files Coverage
1 38129323950.1 11 Oct 2026 09:43AM UTC 16
100.0
GitHub Action Run
Source Files on build 38129323950
  • Tree
  • List 16
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • 209aeb26 on github
  • Prev Build on main (#38123332341)
  • Next Build on main (#38129613322)
  • Delete
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