From 5845711c52b6564e03ffb23ef63982d85f1dff46 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Tue, 24 Mar 2026 17:13:29 +0000
Subject: [PATCH] Version Packages

---
 .changeset/fix-started-step-on-complete.md | 5 -----
 packages/js-api/CHANGELOG.md               | 6 ++++++
 packages/js-api/package.json               | 2 +-
 3 files changed, 7 insertions(+), 6 deletions(-)
 delete mode 100644 .changeset/fix-started-step-on-complete.md

diff --git a/.changeset/fix-started-step-on-complete.md b/.changeset/fix-started-step-on-complete.md
deleted file mode 100644
index 75da5d5b..00000000
--- a/.changeset/fix-started-step-on-complete.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@frigade/js": patch
----
-
-Send STARTED_STEP event for the next step when completing/skipping a step. Previously, `complete()` and `skip()` optimistically marked the next step as started in local state but did not send the STARTED_STEP event to the API, which caused a subsequent `start()` call to no-op.
diff --git a/packages/js-api/CHANGELOG.md b/packages/js-api/CHANGELOG.md
index ee09d548..1d4deceb 100644
--- a/packages/js-api/CHANGELOG.md
+++ b/packages/js-api/CHANGELOG.md
@@ -1,5 +1,11 @@
 # @frigade/js
 
+## 0.9.7
+
+### Patch Changes
+
+- 2723c81: Send STARTED_STEP event for the next step when completing/skipping a step. Previously, `complete()` and `skip()` optimistically marked the next step as started in local state but did not send the STARTED_STEP event to the API, which caused a subsequent `start()` call to no-op.
+
 ## 0.9.6
 
 ### Patch Changes
diff --git a/packages/js-api/package.json b/packages/js-api/package.json
index cec28f6d..2f3fb531 100644
--- a/packages/js-api/package.json
+++ b/packages/js-api/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@frigade/js",
-  "version": "0.9.6",
+  "version": "0.9.7",
   "description": "The official Javascript SDK for Frigade.",
   "type": "module",
   "main": "./dist/index.js",