From 2401d407554a424a85fd8ad83a95200b1029a289 Mon Sep 17 00:00:00 2001 From: Reinaldy Rafli Date: Tue, 30 Apr 2024 01:46:14 +0700 Subject: [PATCH] docs(self-hosted): avoid version confusion by specifying that we assume the version (#1256) --- src/docs/self-hosted/index.mdx | 2 ++ src/docs/self-hosted/releases.mdx | 1 + 2 files changed, 3 insertions(+) diff --git a/src/docs/self-hosted/index.mdx b/src/docs/self-hosted/index.mdx index 53abad6da8..b77485172b 100644 --- a/src/docs/self-hosted/index.mdx +++ b/src/docs/self-hosted/index.mdx @@ -13,6 +13,8 @@ Our recommendation is to download the [latest release of the self-hosted reposi To have easy maintainability for future upgrades, it is recommended to use Git workflow by cloning the self-hosted repository and check out to a specific CalVer tag. More about this on [Releases & Upgrading](/self-hosted/releases/). ```bash +# Assuming current latest version is 24.1.0 +# Current actual version can be acquired from the Releases page on GitHub VERSION="24.1.0" git clone https://github.com/getsentry/self-hosted.git cd self-hosted diff --git a/src/docs/self-hosted/releases.mdx b/src/docs/self-hosted/releases.mdx index 8a3deea5af..a42dfad8f8 100644 --- a/src/docs/self-hosted/releases.mdx +++ b/src/docs/self-hosted/releases.mdx @@ -35,6 +35,7 @@ Before starting the upgrade, we shut down all the services and then run some dat If you downloaded self-hosted repository using Git clone, the upgrade commands should look like this: ```bash +# Assuming your destination upgrade version is 24.3.0 VERSION="24.3.0" git fetch git checkout ${VERSION}