zostera / django-marina / 38123616044

100%

push

github

packaging: start a propagation branch from main, never a release branch (#693)

django-bootstrap4 and django-bootstrap5 both ended up with a version number on
main that was never published. The cause was the same in each: the propagation
PR was branched off the open release branch, so it carried the release commit,
and the dated heading and version bump merged with the workflow change. The
release PR was then closed as redundant because its content was already on
main. bootstrap4 also kept a uv.lock that still named the old version, because
the bump never went through a release PR that runs just build.

That was my doing, in zostera/django-bootstrap4#899 and
zostera/django-bootstrap5#878, and the stacking had a reason: branching off
main risks git merging a new Unreleased entry into a section the release has
since dated, which it does silently because the two sides touch different
lines. PACKAGING.md now names both hazards and says which one to prefer, so the
next person does not trade one for the other by accident.

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

28 of 28 branches covered (100.0%)

Branch coverage included in aggregate %.

164 of 164 relevant lines covered (100.0%)

15.0 hits per line