From b44cef0e66fa02f76f7fa69c045a54f371d2c908 Mon Sep 17 00:00:00 2001 From: James Rasell Date: Fri, 29 Sep 2023 08:31:14 +0100 Subject: [PATCH] docs: make upgrade version detail clearer. (#18608) Co-authored-by: Luiz Aoqui --- website/content/docs/upgrade/index.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/upgrade/index.mdx b/website/content/docs/upgrade/index.mdx index cdbd3b206..dd5d9c0e2 100644 --- a/website/content/docs/upgrade/index.mdx +++ b/website/content/docs/upgrade/index.mdx @@ -13,8 +13,8 @@ version to the next. Upgrades should cause neither a Nomad nor a service outage. However, there are some restrictions to be aware of before upgrading: - Nomad strives to be backward compatible for at least 1 point release, so - Nomad v0.10 hosts work with v0.9 hosts. Upgrading 2 point releases (eg v0.8 - to v0.10) may work but is untested and unsupported. + Nomad v1.6.x hosts work with v1.5.x hosts. Upgrading 2 point releases + (for example, from v1.4.0 to v1.6.0) may work but is untested and unsupported. - Nomad does _not_ support downgrading at this time. Downgrading clients requires draining allocations and removing the [data directory][data_dir].