From 0897ee37819b7749b933c2226d7c18a1e5eb598f Mon Sep 17 00:00:00 2001 From: bherbruck Date: Wed, 14 Oct 2026 08:17:48 -0400 Subject: [PATCH] docs: clear the release notes carried into 0.10.0 (#1054) --- docs/releasing.md | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/docs/releasing.md b/docs/releasing.md index 62db4b55..92e904e0 100644 --- a/docs/releasing.md +++ b/docs/releasing.md @@ -107,17 +107,7 @@ it at the draft's target commit. Items to carry into the next release's notes (step 3 below), then remove from here: -- **Security (agents and the control channel, [#205](https://github.com/bherbruck/solidcraft/issues/205)).** - Upgrading is recommended for anyone who drives SolidCraft from an AI agent or runs it with - `--control` on a shared machine. MCP tool calls now reach files only in the open design's - folder (inside home, without its hidden files), SolidCraft's recovery folder and folders - given with `--allow-path`; `..`, symlinks that lead out and Windows UNC, device, stream and - short-name paths are refused ([#578](https://github.com/bherbruck/solidcraft/pull/578), thanks - @kravens). `doc.recovery_discard` deletes only real recovery entries. The control port now - needs a per-launch token from a file only the user can read, so other local users can't drive - the app; `solidcraft-cli mcp --connect` finds it by itself, other clients must send it (see - docs/control-protocol.md). MCP tool annotations no longer understate side effects. Reported by - @CalvinEthos. +- None yet. ## Verify and publish