From 4d986bfbbcc68bd12bc3b7d6f853d336ea71caa1 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Fri, 14 Aug 2026 03:57:21 +0000
Subject: [PATCH] Version Packages

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

diff --git a/.changeset/quiet-runner-follow.md b/.changeset/quiet-runner-follow.md
deleted file mode 100644
index 2ae4a6015..000000000
--- a/.changeset/quiet-runner-follow.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@qawolf/cli": minor
----
-
-`qawolf runner run --follow` now reports only the run's status — an "in progress" line, then whether it passed or failed — instead of streaming every log line the run produces. The full log stream is available behind the new `--logs` flag, and two more flags mirror further streams into the follow as JSON lines: `--run-events` for the run's progress events and `--recorder-events` for the browser actions the runner records after an anchor taken just before submission. Each stream flag implies `--follow`. Anything parsing a followed run's stdout should expect at most one in-progress status entry by default and read the outcome from the exit code; pass `--logs` to keep receiving log lines, and follow one stream flag at a time when parsing — combined mirrors interleave without a stream label.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 5b4d60943..5ddeab3b6 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,11 @@
 # @qawolf/cli
 
+## 1.10.0
+
+### Minor Changes
+
+- 05e2572: `qawolf runner run --follow` now reports only the run's status — an "in progress" line, then whether it passed or failed — instead of streaming every log line the run produces. The full log stream is available behind the new `--logs` flag, and two more flags mirror further streams into the follow as JSON lines: `--run-events` for the run's progress events and `--recorder-events` for the browser actions the runner records after an anchor taken just before submission. Each stream flag implies `--follow`. Anything parsing a followed run's stdout should expect at most one in-progress status entry by default and read the outcome from the exit code; pass `--logs` to keep receiving log lines, and follow one stream flag at a time when parsing — combined mirrors interleave without a stream label.
+
 ## 1.9.2
 
 ### Patch Changes
diff --git a/package.json b/package.json
index d2057f7b8..1ed782a18 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@qawolf/cli",
-  "version": "1.9.2",
+  "version": "1.10.0",
   "description": "Run and manage QA Wolf flows from the terminal, CI, or an AI agent",
   "keywords": [
     "automation",