flan 8c1b4c45f5 release: rc notes resolve to the base version; publish without jq ...

release_notes.py 'notes v0.6.0-rc1' looked for a CHANGELOG section literally named
v0.6.0-rc1. check() already used base_version(); extract_notes() did not. So the
release workflow cut the tag, passed every gate, and then died extracting the body --
the candidate existed but was never published.

Caught in an rc, which is the entire point of having them.

Also: the Gitea publish and issue steps used jq, which is not guaranteed on a
self-hosted runner. A publish step that dies on a missing tool leaves a tag with no
release behind it, and a bug report that dies on one is a warning system that does
not warn. Both now use python3, which setup-python guarantees.

2026-07-13 18:38:02 +00:00

..

compat.py

compat: check the middlewared METHODS we call, not just the symbols we wrap

2026-07-13 18:25:14 +00:00

release_gate.py

Audit fixes: a compat verdict must never be able to brick a working box

2026-07-13 17:58:15 +00:00

release_notes.py

release: rc notes resolve to the base version; publish without jq

2026-07-13 18:38:02 +00:00