From d41d5311193c8f1350b8f7c1460b6293948e5659 Mon Sep 17 00:00:00 2001
From: dawn <dawn@tangled.org>
Date: Sat, 4 Jul 2026 18:21:57 +0300
Subject: [PATCH] appview,docs: spindle pipelines migration

Signed-off-by: dawn <dawn@tangled.org>
---
 appview/db/db.go |  7 +++++++
 docs/DOCS.md     | 19 +++++++++++++++++++
 2 files changed, 26 insertions(+)

diff --git a/appview/db/db.go b/appview/db/db.go
index c7313f53..03afc7b1 100644
--- a/appview/db/db.go
+++ b/appview/db/db.go
@@ -2421,6 +2421,13 @@ func Make(ctx context.Context, dbPath string) (*DB, error) {
 		return err
 	})
 
+	orm.RunMigration(conn, logger, "spindle-pipeline-ownership-migration", func(tx *sql.Tx) error {
+		_, err := tx.Exec(`
+			update spindles set needs_upgrade = 1;
+		`)
+		return err
+	})
+
 	return &DB{
 		db,
 		logger,
diff --git a/docs/DOCS.md b/docs/DOCS.md
index 86b57979..b72602bc 100644
--- a/docs/DOCS.md
+++ b/docs/DOCS.md
@@ -2124,6 +2124,25 @@ This document is laid out in reverse-chronological order.
 Newer migration guides are listed first, and older guides
 are further down the page.
 
+## Upgrading to v1.16.0-alpha
+
+Starting with v1.16.0-alpha, spindles own CI pipeline data
+directly. The appview no longer stores pipeline runs or follows
+spindle event streams for pipeline history. Instead, it asks the
+configured spindle for pipeline lists, single pipeline details,
+workflow logs, retries, and cancellations over XRPC.
+
+This means that existing pipeline logs / runs won't appear after
+you upgrade. Existing pipeline history from the appview cannot be
+automatically migrated. If you want to migrate your data, you can
+reach out to us and we will send you an SQL file that'll add the data
+into your spindle.
+
+- Upgrade to the latest tag (v1.16.0 or above)
+- Head to the [spindle
+  dashboard](https://tangled.org/settings/spindles) and hit the
+  "retry" button to verify your spindle
+
 ## Upgrading to v1.15.0-alpha
 
 With v1.15.0-alpha, a knot itself owns its members and
-- 
2.51.2