v0.4.6 — the release is the tag message now
Pre-release
Publishing a release used to be a manual gh release create and it drifted
the way manual steps do: v0.4.3 and v0.4.4 never got one, and v0.4.4 is not
even an annotated tag. The tag message is now the single place a release is
described — this text is the proof, since it became the release you are
reading.
The subject line becomes the title and the body becomes the notes. Where the
subject omits the version prefix, the job supplies it. A lightweight tag is
refused in the gating job, before anything is built and before GitHub Pages is
touched, because discovering it at the end would leave a half-finished release
that re-running cannot fix.
The first attempt at this tag caught a bug in the automation itself.
actions/checkout leaves the tag ref pointing at the commit rather than the tag
object, so the annotation was not there to read and every annotated tag looked
lightweight; left unguarded it would have titled this release after a merge
commit. Both places that read the tag now fetch it explicitly first.
The built site is attached here as a zip, so whoever deploys can take it from
the release page rather than digging a 90-day artifact out of a workflow run.
It also puts the object the AGPL and LGPL notices inside it describe next to
the source it was built from.
No application code changed since v0.4.5. This build differs only in the
revision stamp, so production does not need redeploying: xnotary.digital is
running v0.4.5 and that remains correct.