From c53a0949fcd0752a355527c6512fb840ba6b2839 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Mon, 3 Aug 2026 17:25:30 +0000
Subject: [PATCH] Version Packages

---
 .changeset/stop-broken-config.md | 5 -----
 CHANGELOG.md                     | 6 ++++++
 package.json                     | 2 +-
 3 files changed, 7 insertions(+), 6 deletions(-)
 delete mode 100644 .changeset/stop-broken-config.md

diff --git a/.changeset/stop-broken-config.md b/.changeset/stop-broken-config.md
deleted file mode 100644
index d67a843..0000000
--- a/.changeset/stop-broken-config.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@bootnodedev/cbn": patch
----
-
-`stop` no longer requires a fully valid config: it reads only `composeProjectName` and tears the stack down by Compose project label (`docker compose -p <name> down --remove-orphans`), so a broken config can still stop a running stack. If `composeProjectName` itself is missing or invalid, `stop` fails with the usual config error. All other Docker commands still validate the full config.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index ae3d818..a7f0f94 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,11 @@
 # @bootnodedev/cbn
 
+## 0.2.1
+
+### Patch Changes
+
+- a210900: `stop` no longer requires a fully valid config: it reads only `composeProjectName` and tears the stack down by Compose project label (`docker compose -p <name> down --remove-orphans`), so a broken config can still stop a running stack. If `composeProjectName` itself is missing or invalid, `stop` fails with the usual config error. All other Docker commands still validate the full config.
+
 ## 0.2.0
 
 ### Minor Changes
diff --git a/package.json b/package.json
index 91894bc..303ca82 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@bootnodedev/cbn",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "type": "module",
   "description": "Barebones one-click Canton developer stack.",
   "bin": {