pleroma

commit: 633a76b5b3b9f8edfa7f342e00a992016e3284c0
parent f60cb0f77145bf480c67e30ba8b356afda5834ab
Author: lain <lain@soykaf.club>
Date:   Tue,  6 Dec 2022 20:13:55 +0000

Merge branch 'jrabbit-develop-patch-67125' into 'develop'

Upgrade docs improvement: reccomend tagged releases over pulling stable branch

See merge request pleroma/pleroma!3800
Diffstat:
M
docs/administration/updating.md
2
+-

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/administration/updating.md b/docs/administration/updating.md
@@ -17,7 +17,7 @@ su pleroma -s $SHELL -lc "./bin/pleroma_ctl migrate"
 ## For from source installations (using git)
 
 1. Go to the working directory of Pleroma (default is `/opt/pleroma`)
-2. Run `git pull` [^1]. This pulls the latest changes from upstream.
+2. Run `git checkout <tagged release>` [^1]. e.g. `git checkout v2.4.5` This pulls the [tagged release](https://git.pleroma.social/pleroma/pleroma/-/releases) from upstream.
 3. Run `mix deps.get` [^1]. This pulls in any new dependencies.
 4. Stop the Pleroma service.
 5. Run `mix ecto.migrate` [^1] [^2]. This task performs database migrations, if there were any.