doc: new v8 rc guide

docs/abra/upgrade.md

@@ -18,9 +18,29 @@ abra upgrade --rc
 
 ## Migration guides
 
-### `0.6.x-beta` -> `0.7.x-beta`
+> General release notes are [here](https://git.coopcloud.tech/coop-cloud/abra/releases/)
 
-> General release notes are [here](https://git.coopcloud.tech/coop-cloud/abra/releases/tag/0.7.0-beta)
+### `0.7.x-beta` -> `0.8.x-beta`
+
+> Currently still a release candidate! Please help test 😌
+
+- We now have an `--offline` flag instead of relying on internal logic to try
+  to decide when offline/online works best. It's up to you! A lot of `abra`
+  operations require network access, so it is not really truly "offline". The
+  logic prefers local filesystem access when this flag is passed. E.g. if there
+  is a local copy of the catalogue, then don't `git pull`.
+
+- There is a new linting rule for catching invalid tags in recipe versions.
+  This is an seemingly unavoidable issue that requires some maintenance work.
+  If you run into the error, here's some
+  [docs](https://docs.coopcloud.tech/maintainers/handbook/#r014-invalid-lightweight-tag)
+  to help work through it.
+
+- `~/.abra/catalogue` is now *only* updated via `git pull`. You may need to
+  `~/.abra/catalogue && git checkout .` to get `abra` to stop complaining about
+  unstaged changes.
+
+### `0.6.x-beta` -> `0.7.x-beta`
 
 - **ALERTA, ALERTA**, security related issue: all `$domain.env` env vars are now exposed to the deployment via the `app` service container. Each `FOO=BAR` is exported within the context of the container. If you have any privately committed secrets in your `.env` files, please migrate them to the `secrets: ...` configuration in the recipe. This change was made to facilitate tooling which can support auto-upgrading of apps in a deployment.