Skip to content

[9.0] Updates archive again (#209828)#210643

Merged
kibanamachine merged 1 commit intoelastic:9.0from
kibanamachine:backport/9.0/pr-209828
Feb 11, 2025
Merged

[9.0] Updates archive again (#209828)#210643
kibanamachine merged 1 commit intoelastic:9.0from
kibanamachine:backport/9.0/pr-209828

Conversation

@kibanamachine
Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 9.0:

Questions ?

Please refer to the Backport tool documentation

fix elastic#158318

Upgrading from `8.18.0` to `9.1.0` is not a supported upgrade path, nor
is upgrading from `8.19.0` to `9.0.0`.

These awkward upgrade paths have the unfortunate side effect that
migrations integration tests running against certain data archives fail
during backports, depending on the versions they're being backported
from and to.

This PR updates an archive to `8.19.0` in the hope that it will not
cause failures on backports from main to 9.0.0

---------

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: Alejandro Fernández Haro <afharo@gmail.com>
(cherry picked from commit 0b4d43e)
@kibanamachine kibanamachine added the backport This PR is a backport of another PR label Feb 11, 2025
@kibanamachine kibanamachine enabled auto-merge (squash) February 11, 2025 17:20
@kibanamachine kibanamachine merged commit 38bf45f into elastic:9.0 Feb 11, 2025
4 checks passed
@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

cc @TinaHeiligers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants