Updates archive again #209828
Merged
Updates archive again #209828
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Moved back to draft to see if we can resolve failures by skipping on main and not skipping on 9.0. |
|
@elasticmachine merge upstream |
afharo
approved these changes
Feb 11, 2025
...ration_tests/saved_objects/migrations/group3/incompatible_cluster_routing_allocation.test.ts
Outdated
Show resolved
Hide resolved
…up3/incompatible_cluster_routing_allocation.test.ts Co-authored-by: Alejandro Fernández Haro <afharo@gmail.com>
|
Starting backport for target branches: 9.0 https://github.com/elastic/kibana/actions/runs/13268585966 |
💚 Build Succeeded
Metrics [docs]
History
|
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 11, 2025
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)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Feb 11, 2025
# Backport This will backport the following commits from `main` to `9.0`: - [Updates archive again (#209828)](#209828) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Christiane (Tina) Heiligers","email":"christiane.heiligers@elastic.co"},"sourceCommit":{"committedDate":"2025-02-11T17:14:15Z","message":"Updates archive again (#209828)\n\nfix https://github.com/elastic/kibana/issues/158318\r\n\r\nUpgrading from `8.18.0` to `9.1.0` is not a supported upgrade path, nor\r\nis upgrading from `8.19.0` to `9.0.0`.\r\n\r\nThese awkward upgrade paths have the unfortunate side effect that\r\nmigrations integration tests running against certain data archives fail\r\nduring backports, depending on the versions they're being backported\r\nfrom and to.\r\n\r\nThis PR updates an archive to `8.19.0` in the hope that it will not\r\ncause failures on backports from main to 9.0.0\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Alejandro Fernández Haro <afharo@gmail.com>","sha":"0b4d43e24622e72a9975c108fa6713b120311263","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v9.1.0"],"title":"Updates archive again","number":209828,"url":"https://github.com/elastic/kibana/pull/209828","mergeCommit":{"message":"Updates archive again (#209828)\n\nfix https://github.com/elastic/kibana/issues/158318\r\n\r\nUpgrading from `8.18.0` to `9.1.0` is not a supported upgrade path, nor\r\nis upgrading from `8.19.0` to `9.0.0`.\r\n\r\nThese awkward upgrade paths have the unfortunate side effect that\r\nmigrations integration tests running against certain data archives fail\r\nduring backports, depending on the versions they're being backported\r\nfrom and to.\r\n\r\nThis PR updates an archive to `8.19.0` in the hope that it will not\r\ncause failures on backports from main to 9.0.0\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Alejandro Fernández Haro <afharo@gmail.com>","sha":"0b4d43e24622e72a9975c108fa6713b120311263"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209828","number":209828,"mergeCommit":{"message":"Updates archive again (#209828)\n\nfix https://github.com/elastic/kibana/issues/158318\r\n\r\nUpgrading from `8.18.0` to `9.1.0` is not a supported upgrade path, nor\r\nis upgrading from `8.19.0` to `9.0.0`.\r\n\r\nThese awkward upgrade paths have the unfortunate side effect that\r\nmigrations integration tests running against certain data archives fail\r\nduring backports, depending on the versions they're being backported\r\nfrom and to.\r\n\r\nThis PR updates an archive to `8.19.0` in the hope that it will not\r\ncause failures on backports from main to 9.0.0\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Alejandro Fernández Haro <afharo@gmail.com>","sha":"0b4d43e24622e72a9975c108fa6713b120311263"}}]}] BACKPORT--> Co-authored-by: Christiane (Tina) Heiligers <christiane.heiligers@elastic.co>
kapral18
added a commit
to agusruidiazgd/kibana
that referenced
this pull request
Feb 11, 2025
…on-206439 * main: (402 commits) [Search]: Fix Number type field to have correct property (elastic#210462) Change filter for rule monitoring gaps (elastic#209983) Update Logs Explorer deprecation messages (elastic#201307) [APM] Remove `error.id` in `getErrorGroupMainStatistics` query as it's not used (elastic#210613) [Embeddable] Fix presentation panel styles (elastic#210113) [ci] enable Scout reporter for on-merge-unsupported-ftrs (elastic#210627) [Fix][Synonyms UI]Add navigation link to the Detail breadcrumb. (elastic#209574) chore(dep): bump `store2` from `2.12.0` to `2.14.4` (elastic#210530) [scout] adding test helper `@kbn/scout-oblt` package and uptate onboarding tests (elastic#209761) [Cloud Security] Asset Inventory table flyout controls (elastic#208452) [ML] Fix model deployment check in file uploader (elastic#209585) Updates archive again (elastic#209828) [Security Solution] Added concurrency limits and request throttling to prebuilt rule routes (elastic#209551) [Search] [Onboarding] Update search api to use EventEmitter instead of Provider (elastic#209784) [maps] lazy load map actions (elastic#210252) [Cloud Security] Adding telemetry collection condition based on render condition (elastic#208758) [Solution nav] Use flyout for Stack Management in Search and Observability solutions (elastic#208632) [Search] Fix Add Inference Endpoint API call (elastic#210243) [Agentless Connectors] Integration overview panel (elastic#210222) [Lens] Restore dynamic colouring by value for Last value agg (elastic#209110) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix #158318
Upgrading from
8.18.0to9.1.0is not a supported upgrade path, nor is upgrading from8.19.0to9.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.0in the hope that it will not cause failures on backports from main to 9.0.0