Skip to content

Commit 77c91cd

Browse files
committed
Add upgrade note about release date constraint
We don't support (and will actively block) upgrades to chronologically-older versions. This commit adds a note in the docs about this.
1 parent a6680b2 commit 77c91cd

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

docs/reference/upgrade.asciidoc

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,18 @@ proceeding with the upgrade. For instructions, refer to
2525
{stack-ref}/upgrading-elastic-stack.html#prepare-to-upgrade[Prepare to upgrade
2626
from 7.x].
2727

28+
[discrete]
29+
[[upgrade-newer-releases]]
30+
=== Out-of-order releases
31+
32+
Elastic maintains several minor versions of {es} at once, so releases do not
33+
always happen in order of their version numbers. You can only upgrade to
34+
{version} if the version you are currently running has an older version number
35+
than {version} _and_ has an earlier release date than {version}.
36+
37+
If you are currently running a version with an older version number but a later
38+
release date than {version}, wait for a newer release before upgrading.
39+
2840
[discrete]
2941
[[upgrade-index-compatibility]]
3042
=== Index compatibility

0 commit comments

Comments
 (0)