+7

appview/db/db.go

Reviewed

··· 2240 2240 return err 2241 2241 }) 2242 2242 2243 2243 + orm.RunMigration(conn, logger, "migrate-knots-to-knot-owned-acl", func(tx *sql.Tx) error { 2244 2244 + _, err := tx.Exec(` 2245 2245 + update registrations set needs_upgrade = 1; 2246 2246 + `) 2247 2247 + return err 2248 2248 + }) 2249 2249 + 2243 2250 return &DB{ 2244 2251 db, 2245 2252 logger,

+19

docs/DOCS.md

Reviewed

··· 1620 1620 Newer migration guides are listed first, and older guides 1621 1621 are further down the page. 1622 1622 1623 1623 + ## Upgrading to v1.15.0-alpha 1624 1624 + 1625 1625 + With v1.15.0-alpha, a knot itself owns its members and 1626 1626 + per-repo collaborators directly. Previously this data was sourced from 1627 1627 + PDS records (`sh.tangled.knot.member` and `sh.tangled.repo.collaborator`) 1628 1628 + that the appview and the knot both read off the firehose. 1629 1629 + The knot is now the source of truth and serves them over XRPC instead: 1630 1630 + 1631 1631 + - `sh.tangled.knot.addMember`, `sh.tangled.knot.removeMember`, `sh.tangled.knot.listMembers` 1632 1632 + - `sh.tangled.repo.addCollaborator`, `sh.tangled.repo.removeCollaborator`, `sh.tangled.repo.listCollaborators` 1633 1633 + 1634 1634 + Until your knot is upgraded, the appview keeps reading its 1635 1635 + members and collaborators from the old firehose-sourced records. 1636 1636 + Upgrade to move your knot onto knot-owned access control. 1637 1637 + 1638 1638 + - Upgrade to the latest tag (v1.15.0 or above) 1639 1639 + - Head to the [knot dashboard](https://tangled.org/settings/knots) and 1640 1640 + hit the "retry" button to verify your knot 1641 1641 + 1623 1642 ## Upgrading to v1.14.0-alpha 1624 1643 1625 1644 Starting with v1.14.0-alpha, the fully knot uses the repoDID as its