eric/ReleaseKit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Prepare ReleaseKit hosted-page delivery

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-05 20:56:57 +00:00
parent 9e619c98a4
commit d0247d1ccb
8 changed files with 228 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/policy/release.md
View File

@@ -41,12 +41,16 @@ A failed or ambiguous push requires resolving the authoritative remote state
before declaring success or retrying; successful pushes do not require a
separate remote read-back gate.
ReleaseKit's initial deliverable is source only. Distributing executable builds
requires a deliberate update identifying the deliverables, selected targets,
and automation responsibilities. Supporting cross-builds for consumers does not
declare ReleaseKit binaries. Additional declared deliverables may be published
asynchronously from the tagged source, must be traceable to that source, and
must identify the same version.
ReleaseKit's deliverables are its immutable source tag and a hosted Gitea
release page whose body is the complete checked-in release note. A prepared
Woodpecker workflow builds the local release tool from that tagged source and
delivers the note page. This adds no executable download or binary manifest.
Any later distribution of executable builds requires a deliberate update
identifying the deliverables, selected targets, and automation responsibilities.
Supporting cross-builds for consumers does not declare ReleaseKit binaries.
Additional declared deliverables may be published asynchronously from the
tagged source, must be traceable to that source, and must identify the same
version.
Track source-release completion and artifact delivery separately. Report delivery
failures and optional investigations under artifact-delivery status.