base-layer/releasekit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 5 Wiki Activity

Clarify ReleaseKit ownership of remediation work

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-01 21:52:51 +00:00
parent 1ad6ddc198
commit 5d5653bfc3
1 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/roadmap/remediation.md
View File

@@ -22,6 +22,20 @@ when it reduces caller-owned release work. In particular, callers can reuse a
repository location across preparation and subsequent orchestration without repository location across preparation and subsequent orchestration without
normalization code or another configuration option. normalization code or another configuration option.
Preparation owns checkout-root resolution when the supplied location is inside
a checkout. Ordinary root-module callers keep the same request shape; callers
selecting a nested module supply its repository-relative `ModuleDir`.
Standalone preparation retains the supplied directory as its base. This is the
selected approach to the preparation-anchor question.
Apply the same ownership principle to the other corrections: ReleaseKit
validates derived tags, prepares the selected module's dependencies, preserves
cancellation and uncertain publication outcomes, and classifies backend
observations. Consumers continue to use the existing operations and outcomes.
The empty-prebuilt and verification-order findings call for documentation that
accurately explains existing behavior. Evaluate each correction by whether an
ordinary consumer can use it without additional release code or configuration.
The existing public orchestration and runtime facades and internal package The existing public orchestration and runtime facades and internal package
boundaries remain appropriate. These corrections use the existing public types, boundaries remain appropriate. These corrections use the existing public types,
receipt schema, module/tag conventions, and publication/delivery model. receipt schema, module/tag conventions, and publication/delivery model.