Centralize release tool invocation
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Release tooling implementation plan
|
||||
|
||||
Status: Stage 1 complete; Stages 2–6 pending.
|
||||
Status: Stages 1–2 complete; Stages 3–6 pending.
|
||||
|
||||
Follow the stages in integer order. This is one end-to-end sprint: intermediate
|
||||
stages may temporarily leave scripts, tests, and documentation inconsistent.
|
||||
@@ -80,6 +80,10 @@ entirely by the existing upstream profile schema.
|
||||
|
||||
## Stage 2: Centralize tool invocation and module routing
|
||||
|
||||
**Completed.** Both scripts pass shell syntax checks; a fake Go invocation
|
||||
confirmed representative publication and raw-command forwarding. Focused
|
||||
coverage follows in Stage 3.
|
||||
|
||||
Create executable POSIX-shell `scripts/releasekit` as the shared entry point.
|
||||
Keep executable `scripts/release` as the existing publication convenience entry
|
||||
point. No shell library, module-map file, generated script, or JSON parser is
|
||||
|
||||
Reference in New Issue
Block a user