zostera / django-bootstrap3 / 38129308782

100%

push

github

Restore two changes lost to a squash merge (#1166)

Both were pushed to the sync-release-preflight branch after #1165 had already
squash-merged, so they never reached main. My mistake: I pushed to a branch
whose pull request was closed, and the green checks I then polled were that
merged pull request's, which read as confirmation that the new commits had
landed. They had not.

The 3.15 entry no longer calls a released Python a release candidate. This one
matters before 26.3 is cut, because the entry is still in Unreleased here,
where it can be fixed. django-icons and django-bootstrap4 both published that
sentence; their dated sections stay as they are, since a release section
records what was said at the time.

MAINTAINING.md gains the note that release-check reporting no Unreleased
entries straight after a cut means nothing is pending, not that the changelog
was lost.

django-icons lost the same MAINTAINING note the same way and gets its own
restore. django-bootstrap5 is unaffected, its sync pull request is still open
and carries both commits.

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

252 of 252 branches covered (100.0%)

Branch coverage included in aggregate %.

748 of 748 relevant lines covered (100.0%)

15.0 hits per line