Record Audita delivery migration
This commit is contained in:
@@ -581,6 +581,20 @@ a declared ReleaseKit dependency uses the installed-tool integration.
|
||||
|
||||
## Stage 14: Migrate Audita's local CI integration
|
||||
|
||||
**Completion:** Complete. Audita commit `17421bc` makes both local and hosted
|
||||
bootstraps resolve ReleaseKit v0.1.0 from the consumer's module configuration.
|
||||
The existing Go image, `GITEA_RELEASE_TOKEN` secret, release profile, caller
|
||||
arguments, and native tool status are preserved. The local wrapper uses
|
||||
temporary alternate module metadata and cleans it up before executing the tool.
|
||||
Audita's runbook now describes the module-selected workflow.
|
||||
|
||||
**Verification:** Audita's `go test ./scripts -count=1`,
|
||||
`bash -n scripts/release.sh`, and real `bash scripts/release.sh version` passed;
|
||||
the wrapper reported `releasekit v0.1.0` and left source module files unchanged.
|
||||
ReleaseKit's `TestWoodpeckerTagDeliveryTemplate` and
|
||||
`TestWoodpeckerTagDeliveryUsesTaggedModuleVersion` passed with local Git and
|
||||
module-proxy fixtures. Both repositories passed their relevant diff checks.
|
||||
|
||||
**Outcome:** Audita's local wrapper and CI select the same module-declared tool.
|
||||
|
||||
1. Read `../audita` orientation/policies and inspect its worktree before editing.
|
||||
|
||||
Reference in New Issue
Block a user