The dist-zip job built the linux/amd64 zip and uploaded it as an Actions
artifact, then stopped. An artifact is reachable only from the run's page,
behind an Actions login, and expires after 90 days -- so every release since
the zip job landed produced a download an operator could not find. The one
Release on this repo (archied/v1.22.0) was created by hand and carries no
asset at all: nothing in CI has ever created one.
Publish the Release from this job and attach the zip:
- Job-level `permissions: contents: write`. The workflow default is
contents:read, so a publish step would fail without it; scoping it to this
job keeps the build-and-push jobs read-only.
- The body is this version's changelog section, extracted from the "## [x.y.z]"
heading to the next "## [" heading rather than pasting the whole file. The
changelog stays the single source of truth, and the tag/changelog gate in
`gate` has already proven the section exists.
- Attached to the archied tag, because the zip is named and versioned for
archied; `--follow-tags` pushes both tags at one commit, so the runtime
release is the same commit.
- Idempotent: `gh release view` decides between `create` and
`upload --clobber`, so a retried or superseded deploy run cannot fail on an
existing Release or duplicate the asset.
- Fails loudly when the section extracts empty, rather than publishing a
Release with no notes.