From 08265feefa0261baf812d5db1f7bf49fcb414c49 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Sat, 29 Aug 2026 12:38:15 +0000
Subject: [PATCH] chore: version packages

---
 .changeset/olive-donkeys-jam.md   | 20 --------------------
 packages/adapter-api/CHANGELOG.md | 21 +++++++++++++++++++++
 packages/adapter-api/package.json |  2 +-
 3 files changed, 22 insertions(+), 21 deletions(-)
 delete mode 100644 .changeset/olive-donkeys-jam.md

diff --git a/.changeset/olive-donkeys-jam.md b/.changeset/olive-donkeys-jam.md
deleted file mode 100644
index 682215e..0000000
--- a/.changeset/olive-donkeys-jam.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-'@haverstack/adapter-api': patch
----
-
-Stop the change-feed client reconnecting against a refusal that will repeat.
-
-`isFatalFeedError` ended the reconnect loop only for an unrenewable
-credential (401) and an authorization refusal (403). Every other refusal the
-server faulted the request for — a malformed cursor or filter answered
-`400 bad_request`, say — was treated as transient, so `subscribeChanges()`
-retried it with backoff indefinitely, settling into an attempt roughly every
-15 seconds and reporting the same error to `onError` each time. The
-subscriber was never told to stop, and `onReset` never fired, so the
-application had nothing to reconcile from either.
-
-The predicate now decides on the wire status: a `4xx` ends the loop, since
-the reconnect sends the same request and would be refused the same way. A
-`5xx` still reconnects, which is what keeps `timeout` — the answer a server
-gives while shedding query load — from turning a busy server into a
-permanently dead subscription.
diff --git a/packages/adapter-api/CHANGELOG.md b/packages/adapter-api/CHANGELOG.md
index 418984d..a63c30a 100644
--- a/packages/adapter-api/CHANGELOG.md
+++ b/packages/adapter-api/CHANGELOG.md
@@ -1,5 +1,26 @@
 # @haverstack/adapter-api
 
+## 0.12.2
+
+### Patch Changes
+
+- [#200](https://github.com/haverstack/core/pull/200) [`ddeaaf4`](https://github.com/haverstack/core/commit/ddeaaf426b106e19bb7c8807722f781995a3dd48) Thanks [@cuibonobo](https://github.com/cuibonobo)! - Stop the change-feed client reconnecting against a refusal that will repeat.
+
+  `isFatalFeedError` ended the reconnect loop only for an unrenewable
+  credential (401) and an authorization refusal (403). Every other refusal the
+  server faulted the request for — a malformed cursor or filter answered
+  `400 bad_request`, say — was treated as transient, so `subscribeChanges()`
+  retried it with backoff indefinitely, settling into an attempt roughly every
+  15 seconds and reporting the same error to `onError` each time. The
+  subscriber was never told to stop, and `onReset` never fired, so the
+  application had nothing to reconcile from either.
+
+  The predicate now decides on the wire status: a `4xx` ends the loop, since
+  the reconnect sends the same request and would be refused the same way. A
+  `5xx` still reconnects, which is what keeps `timeout` — the answer a server
+  gives while shedding query load — from turning a busy server into a
+  permanently dead subscription.
+
 ## 0.12.1
 
 ### Patch Changes
diff --git a/packages/adapter-api/package.json b/packages/adapter-api/package.json
index ad126e5..3f9beca 100644
--- a/packages/adapter-api/package.json
+++ b/packages/adapter-api/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@haverstack/adapter-api",
-  "version": "0.12.1",
+  "version": "0.12.2",
   "description": "Remote server adapter for Haverstack",
   "type": "module",
   "exports": {