Skip to content

Conversation

@masseyke
Copy link
Member

DataStreamsUpgradeIT was incorrectly using 8.9 as the minimum version where it could create a data stream lifecycle. That is the version where data stream lifecycles were introduced, but they were behind a feature flag until 8.11.0. This fixes that.
Closes #122033

@masseyke masseyke added >non-issue :Data Management/Data streams Data streams and their lifecycles auto-backport Automatically create backport pull requests when merged v8.18.0 v8.19.0 labels Feb 10, 2025
@elasticsearchmachine elasticsearchmachine added the Team:Data Management Meta label for data/management team label Feb 10, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

@masseyke masseyke enabled auto-merge (squash) February 10, 2025 19:33
@masseyke masseyke merged commit cc8e726 into elastic:8.x Feb 11, 2025
15 checks passed
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

The backport operation could not be completed due to the following error:

An unexpected error occurred when attempting to backport this PR.

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 122207

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

Labels

auto-backport Automatically create backport pull requests when merged :Data Management/Data streams Data streams and their lifecycles >non-issue Team:Data Management Meta label for data/management team v8.18.0 v8.19.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants