From ead8e422113d43c9ee828a92a628783634f65294 Mon Sep 17 00:00:00 2001 From: Jakub Zych Date: Thu, 22 Oct 2026 02:53:07 +0200 Subject: [PATCH] docs(19.8-06): record the go-ahead: release v0.4.2 --- .../19.8-console-commands-overhaul/19.8-06-SUMMARY.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.planning/phases/19.8-console-commands-overhaul/19.8-06-SUMMARY.md b/.planning/phases/19.8-console-commands-overhaul/19.8-06-SUMMARY.md index f6dd6e59..e8bc6058 100644 --- a/.planning/phases/19.8-console-commands-overhaul/19.8-06-SUMMARY.md +++ b/.planning/phases/19.8-console-commands-overhaul/19.8-06-SUMMARY.md @@ -85,4 +85,8 @@ No row asks for a require bump or a regenerate: **plugins and applications get n ## Task 1 reply -(awaiting the user's reply: "release vX.Y.Z", "push-only" or "hold") +The user's reply, verbatim: + +> release + +Read as the recommended option with the proposed tag: **release v0.4.2** (RELEASE_TAG=v0.4.2). The reply authorises an annotated tag v0.4.2 on the tested commit, a fast-forward push of exactly that commit to origin master followed by the tag, the same-day changelog post, the sm-demo-app roadmap snapshot commit and its push (when it is the only unpushed commit there), then the `--all` gate. No force push, no deploy.