Complete module release documentation

This commit is contained in:
2026-10-10 04:03:42 +00:00
parent b49c1f379e
commit 90559fe01b
18 changed files with 260 additions and 45 deletions

View File

@@ -9,6 +9,9 @@ Copy the contents of this directory into a consumer repository root, keeping
the listed module directories and profile paths at those locations, then run
the launcher from that checkout.
The sample modules declare Go 1.26.0, matching the current ReleaseKit consumer
minimum.
`release-modules.tsv` is literal tab-separated text with four columns:
1. Local selector.
@@ -64,4 +67,7 @@ the literal event tag before selecting the module, copies that module's metadata
outside the checkout, and builds the ReleaseKit version selected there. It then
uses `ci-deliver --prepared` with the mapped profile and expected physical module.
The `core-v2` profile demonstrates binary delivery; the other profiles are
page-only.
page-only. Before enabling the workflow, configure each selected profile's
`delivery` destination and add the Woodpecker repository secret
`releasekit_gitea_token`; the workflow exposes it as
`RELEASEKIT_GITEA_TOKEN` only in the delivery step.

View File

@@ -1,5 +1,5 @@
module example.com/multi-module-consumer
go 1.25.0
go 1.26.0
require gitea.maximumdirect.net/eric/ReleaseKit v0.2.197

View File

@@ -1,5 +1,5 @@
module example.com/multi-module-consumer/integrations/ckconfig
go 1.25.0
go 1.26.0
require gitea.maximumdirect.net/eric/ReleaseKit v0.2.197

View File

@@ -1,5 +1,5 @@
module example.com/multi-module-consumer/integrations/core/v2
go 1.25.0
go 1.26.0
require gitea.maximumdirect.net/eric/ReleaseKit v0.2.197