From 9ab7bfe3e3c86f21138d4519d29eab72a14e1973 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Thu, 5 Nov 2026 18:19:38 +0000
Subject: [PATCH] chore(zero-swift): version packages

---
 .changeset/swift-cut-frame-ping.md   | 5 -----
 packages/zero-swift-cli/CHANGELOG.md | 6 ++++++
 packages/zero-swift-cli/package.json | 2 +-
 swift/VERSION                        | 2 +-
 4 files changed, 8 insertions(+), 7 deletions(-)
 delete mode 100644 .changeset/swift-cut-frame-ping.md

diff --git a/.changeset/swift-cut-frame-ping.md b/.changeset/swift-cut-frame-ping.md
deleted file mode 100644
index dc9daec16f..0000000000
--- a/.changeset/swift-cut-frame-ping.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-'zero-swift': patch
----
-
-On Apple platforms, the client now reconnects when the server's connection ends partway through a message, even if URLSession is slow to report the end. URLSession hands over the part of the message it has, and the client used to wait 1 second for the connection to end before deciding the message was really bad. On a busy device URLSession can report the end several seconds later, so the client stopped in `error` instead of reconnecting. The client now sends a WebSocket ping instead. If the ping fails, the message was cut off and the client reconnects. If the pong comes back, the message was really bad and the error stands, as before. If neither comes within 10 seconds, the error also stands.
diff --git a/packages/zero-swift-cli/CHANGELOG.md b/packages/zero-swift-cli/CHANGELOG.md
index 14e88f6a30..e12dab7d04 100644
--- a/packages/zero-swift-cli/CHANGELOG.md
+++ b/packages/zero-swift-cli/CHANGELOG.md
@@ -1,5 +1,11 @@
 # zero-swift
 
+## 0.7.7
+
+### Patch Changes
+
+- 827a7ad: On Apple platforms, the client now reconnects when the server's connection ends partway through a message, even if URLSession is slow to report the end. URLSession hands over the part of the message it has, and the client used to wait 1 second for the connection to end before deciding the message was really bad. On a busy device URLSession can report the end several seconds later, so the client stopped in `error` instead of reconnecting. The client now sends a WebSocket ping instead. If the ping fails, the message was cut off and the client reconnects. If the pong comes back, the message was really bad and the error stands, as before. If neither comes within 10 seconds, the error also stands.
+
 ## 0.7.6
 
 ### Patch Changes
diff --git a/packages/zero-swift-cli/package.json b/packages/zero-swift-cli/package.json
index a6ca4dfccd..07ed53a7d0 100644
--- a/packages/zero-swift-cli/package.json
+++ b/packages/zero-swift-cli/package.json
@@ -1,6 +1,6 @@
 {
   "name": "zero-swift",
-  "version": "0.7.6",
+  "version": "0.7.7",
   "description": "Generates the Swift row types and schema of a Zero app for the Zero Swift client.",
   "license": "Apache-2.0",
   "repository": {
diff --git a/swift/VERSION b/swift/VERSION
index c006218557..879be8a98f 100644
--- a/swift/VERSION
+++ b/swift/VERSION
@@ -1 +1 @@
-0.7.6
+0.7.7