lewis.moe
Monorepo for Tangled
docs: write upgrade guide for v1.8.x
merge all migration guides into one doc
Signed-off-by: oppiliappan <me@oppi.li>
+18
-3
docs/migrations/knot-1.7.0.md
docs/migrations.md
+18
-3
docs/migrations/knot-1.7.0.md
docs/migrations.md
···
1
-
# Upgrading from v1.7.0
2
3
After v1.7.0, knot secrets have been deprecated. You no
4
longer need a secret from the appview to run a knot. All
···
19
hit the "retry" button to verify your knot. This simply
20
writes a `sh.tangled.knot` record to your PDS.
21
22
-
## Nix
23
-
24
If you use the nix module, simply bump the flake to the
25
latest revision, and change your config block like so:
26
···
33
};
34
};
35
```
···
1
+
# Migrations
2
+
3
+
This document is laid out in reverse-chronological order.
4
+
Newer migration guides are listed first, and older guides
5
+
are further down the page.
6
+
7
+
## Upgrading from v1.8.x
8
+
9
+
After v1.8.2, the HTTP API for knots has been deprecated and
10
+
replaced with XRPC. Repositories on outdated knots will not
11
+
be viewable from the appview. Upgrading is straightforward:
12
+
13
+
- Upgrade to latest tag (v1.9.0 or above)
14
+
- Head to the [knot dashboard](https://tangled.sh/knots) and
15
+
hit the "retry" button to verify your knot
16
+
17
+
## Upgrading from v1.7.x
18
19
After v1.7.0, knot secrets have been deprecated. You no
20
longer need a secret from the appview to run a knot. All
···
35
hit the "retry" button to verify your knot. This simply
36
writes a `sh.tangled.knot` record to your PDS.
37
38
If you use the nix module, simply bump the flake to the
39
latest revision, and change your config block like so:
40
···
47
};
48
};
49
```
50
+