+7

appview/db/db.go

Reviewed

··· 2421 2421 return err 2422 2422 }) 2423 2423 2424 2424 + orm.RunMigration(conn, logger, "spindle-pipeline-ownership-migration", func(tx *sql.Tx) error { 2425 2425 + _, err := tx.Exec(` 2426 2426 + update spindles set needs_upgrade = 1; 2427 2427 + `) 2428 2428 + return err 2429 2429 + }) 2430 2430 + 2424 2431 return &DB{ 2425 2432 db, 2426 2433 logger,

+19

docs/DOCS.md

Reviewed

··· 2124 2124 Newer migration guides are listed first, and older guides 2125 2125 are further down the page. 2126 2126 2127 2127 + ## Upgrading to v1.16.0-alpha 2128 2128 + 2129 2129 + Starting with v1.16.0-alpha, spindles own CI pipeline data 2130 2130 + directly. The appview no longer stores pipeline runs or follows 2131 2131 + spindle event streams for pipeline history. Instead, it asks the 2132 2132 + configured spindle for pipeline lists, single pipeline details, 2133 2133 + workflow logs, retries, and cancellations over XRPC. 2134 2134 + 2135 2135 + This means that existing pipeline logs / runs won't appear after 2136 2136 + you upgrade. Existing pipeline history from the appview cannot be 2137 2137 + automatically migrated. If you want to migrate your data, you can 2138 2138 + reach out to us and we will send you an SQL file that'll add the data 2139 2139 + into your spindle. 2140 2140 + 2141 2141 + - Upgrade to the latest tag (v1.16.0 or above) 2142 2142 + - Head to the [spindle 2143 2143 + dashboard](https://tangled.org/settings/spindles) and hit the 2144 2144 + "retry" button to verify your spindle 2145 2145 + 2127 2146 ## Upgrading to v1.15.0-alpha 2128 2147 2129 2148 With v1.15.0-alpha, a knot itself owns its members and