`cargo release patch --execute` now does what the last three releases
did by hand: bump Cargo.toml/Cargo.lock, rewrite PKGBUILD's pkgver,
stamp the "## Unreleased" changelog section with version and date,
commit as "release X.Y.Z", tag vX.Y.Z and push commit and tag to the
gitea remote (not `origin`, which is the GitHub upstream). The tag then
triggers .gitea/workflows/release.yml as before. No crates.io publish.
CHANGELOG.md gets a standing "## Unreleased" section to collect entries
between releases; README documents the flow.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
