Skip to content

Commit e4fb9d4

Browse files
Add upgrade note about release date constraint (#2948)
We don't support (and will actively block) upgrades to chronologically-older versions. This commit adds a note in the docs about this. Co-authored-by: Liam Thompson <[email protected]>
1 parent 0772842 commit e4fb9d4

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

docs/en/install-upgrade/upgrading-stack.asciidoc

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,21 @@ These steps vary based on your current version:
99
* <<prepare-to-upgrade,Upgrade from 7.x>>
1010
endif::[]
1111

12+
[IMPORTANT]
13+
.Out-of-order releases
14+
====
15+
Elastic maintains several minor versions of the Elastic Stack at once. This
16+
means releases do not always happen in order of their version numbers. You can
17+
only upgrade to {version} if the version you are currently running meets both
18+
of these conditions:
19+
20+
* Has an older version number than {version}.
21+
* Has an earlier release date than {version}.
22+
23+
If you are currently running a version with an older version number but a later
24+
release date than {version}, wait for a newer release before upgrading.
25+
====
26+
1227
IMPORTANT: Upgrading from a release candidate build, such as 8.0.0-rc1 or
1328
8.0.0-rc2, is not supported. Pre-releases should only be used for testing in a
1429
temporary environment.

0 commit comments

Comments
 (0)