Repository navigation
Releases
Releases · tebako-packages/xml2rfc
3.34.2-1
ci: OCI mirror-publish leg (dormant) + tools pin v2.8.24 (#23) The publish step gains the ghcr.io mirror leg: when the OCI_REPO repo variable is set, the publish invocation carries --oci and the same staged bytes ride the repo's ghcr package (per-triplet tags, .asc sibling digest-tags, the additive oci: registry locator); unset omits the flag byte-for-byte and the publish is unchanged. The credential is a docker-config auths entry minted from the job's own GITHUB_TOKEN, confined to ghcr.io. packages: write lands at BOTH levels — a job-level block replaces the workflow-level grant, so the release job's grants are restated in full. The tools pin advances v2.8.12 -> v2.8.24 (the first line carrying publish --oci); every digest is verified against the release's own SHA256SUMS. Co-authored-by: tebako-ci <tebako@ribose.com>
3.34.2
commit the windows-ucrt closure lock (the tag run's gate: tags never …
3.34.1
xml2rfc 3.34.1 — python 3.14.7 line, shard-model staging, POSIX six
3.34.0-1
xml2rfc 3.34.0-1 — signed payload line (spec 09 §9), signed python ru…
3.34.0
xml2rfc 3.34.0 — the first payload release (the POSIX six).
Re-tagged onto a4725cc1740642bbf66f160088c75e3b97ad7316 (#3, the registry scaffold parse fix; #2 was the
publish-path mkdir fix) after dispatches 34018018854 + 34018379113 died
on first-run publish-path gaps. Publish dispatched per the owner's
explicit go-ahead ('Proceed with all work!', 2026-09-06 ~06:30Z).