Skip to content

Conversation

afharo
Copy link
Member

@afharo afharo commented Sep 1, 2025

Summary

The ES client's team needs apache-arrow to be on v20, at least.

This PR bumps the ES client's underlying client to that version by using resolutions in the package.json.

Checklist

  • This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
  • Review the backport guidelines and apply applicable backport:* labels.

@afharo afharo requested a review from pquentin September 1, 2025 11:24
@afharo afharo self-assigned this Sep 1, 2025
@afharo afharo added Team:Core Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t// release_note:skip Skip the PR/issue when compiling release notes backport:version Backport to applied version labels v9.1.4 v8.19.4 labels Sep 1, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

Copy link
Member

@pquentin pquentin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! LGTM.

@afharo afharo enabled auto-merge (squash) September 1, 2025 11:33
@afharo afharo merged commit 33851e6 into elastic:main Sep 1, 2025
26 checks passed
@afharo afharo deleted the apache-arrow/ensure-at-least-v20 branch September 1, 2025 13:27
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 8.19, 9.1

https://github.com/elastic/kibana/actions/runs/17379053197

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

cc @afharo

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Sep 1, 2025
## Summary

The ES client's team needs apache-arrow to be on v20, at least.

This PR bumps the ES client's underlying client to that version by using
`resolutions` in the package.json.

### Checklist

- [x] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

(cherry picked from commit 33851e6)
@kibanamachine
Copy link
Contributor

💔 Some backports could not be created

Status Branch Result
8.19 Backport failed because of merge conflicts
9.1

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 233625

Questions ?

Please refer to the Backport tool documentation

kibanamachine added a commit that referenced this pull request Sep 1, 2025
# Backport

This will backport the following commits from `main` to `9.1`:
- [apache-arrow: ensure v20+
(#233625)](#233625)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Alejandro Fernández
Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2025-09-01T13:27:11Z","message":"apache-arrow:
ensure v20+ (#233625)\n\n## Summary\n\nThe ES client's team needs
apache-arrow to be on v20, at least.\n\nThis PR bumps the ES client's
underlying client to that version by using\n`resolutions` in the
package.json.\n\n### Checklist\n\n- [x] This was checked for breaking
HTTP API changes, and any breaking\nchanges have been approved by the
breaking-change committee. The\n`release_note:breaking` label should be
applied in these situations.\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*`
labels.","sha":"33851e69c204d109a8bae40ef1d7eb03b00f7432","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:version","v9.2.0","v9.1.4","v8.19.4"],"title":"apache-arrow:
ensure
v20+","number":233625,"url":"https://github.com/elastic/kibana/pull/233625","mergeCommit":{"message":"apache-arrow:
ensure v20+ (#233625)\n\n## Summary\n\nThe ES client's team needs
apache-arrow to be on v20, at least.\n\nThis PR bumps the ES client's
underlying client to that version by using\n`resolutions` in the
package.json.\n\n### Checklist\n\n- [x] This was checked for breaking
HTTP API changes, and any breaking\nchanges have been approved by the
breaking-change committee. The\n`release_note:breaking` label should be
applied in these situations.\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*`
labels.","sha":"33851e69c204d109a8bae40ef1d7eb03b00f7432"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/233625","number":233625,"mergeCommit":{"message":"apache-arrow:
ensure v20+ (#233625)\n\n## Summary\n\nThe ES client's team needs
apache-arrow to be on v20, at least.\n\nThis PR bumps the ES client's
underlying client to that version by using\n`resolutions` in the
package.json.\n\n### Checklist\n\n- [x] This was checked for breaking
HTTP API changes, and any breaking\nchanges have been approved by the
breaking-change committee. The\n`release_note:breaking` label should be
applied in these situations.\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*`
labels.","sha":"33851e69c204d109a8bae40ef1d7eb03b00f7432"}},{"branch":"9.1","label":"v9.1.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>
@afharo
Copy link
Member Author

afharo commented Sep 1, 2025

💚 All backports created successfully

Status Branch Result
8.19

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

afharo added a commit to afharo/kibana that referenced this pull request Sep 1, 2025
## Summary

The ES client's team needs apache-arrow to be on v20, at least.

This PR bumps the ES client's underlying client to that version by using
`resolutions` in the package.json.

### Checklist

- [x] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

(cherry picked from commit 33851e6)

# Conflicts:
#	package.json
#	yarn.lock
ymao1 pushed a commit to ymao1/kibana that referenced this pull request Sep 2, 2025
## Summary

The ES client's team needs apache-arrow to be on v20, at least.

This PR bumps the ES client's underlying client to that version by using
`resolutions` in the package.json.

### Checklist

- [x] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.
MichelLosier pushed a commit to MichelLosier/kibana that referenced this pull request Sep 2, 2025
## Summary

The ES client's team needs apache-arrow to be on v20, at least.

This PR bumps the ES client's underlying client to that version by using
`resolutions` in the package.json.

### Checklist

- [x] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.
kowalczyk-krzysztof pushed a commit to kowalczyk-krzysztof/kibana that referenced this pull request Sep 3, 2025
## Summary

The ES client's team needs apache-arrow to be on v20, at least.

This PR bumps the ES client's underlying client to that version by using
`resolutions` in the package.json.

### Checklist

- [x] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.
afharo added a commit that referenced this pull request Sep 11, 2025
# Backport

This will backport the following commits from `main` to `8.19`:
- [apache-arrow: ensure v20+
(#233625)](#233625)

<!--- Backport version: 10.0.1 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Alejandro Fernández
Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2025-09-01T13:27:11Z","message":"apache-arrow:
ensure v20+ (#233625)\n\n## Summary\n\nThe ES client's team needs
apache-arrow to be on v20, at least.\n\nThis PR bumps the ES client's
underlying client to that version by using\n`resolutions` in the
package.json.\n\n### Checklist\n\n- [x] This was checked for breaking
HTTP API changes, and any breaking\nchanges have been approved by the
breaking-change committee. The\n`release_note:breaking` label should be
applied in these situations.\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*`
labels.","sha":"33851e69c204d109a8bae40ef1d7eb03b00f7432","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:version","v9.2.0","v9.1.4","v8.19.4"],"title":"apache-arrow:
ensure
v20+","number":233625,"url":"https://github.com/elastic/kibana/pull/233625","mergeCommit":{"message":"apache-arrow:
ensure v20+ (#233625)\n\n## Summary\n\nThe ES client's team needs
apache-arrow to be on v20, at least.\n\nThis PR bumps the ES client's
underlying client to that version by using\n`resolutions` in the
package.json.\n\n### Checklist\n\n- [x] This was checked for breaking
HTTP API changes, and any breaking\nchanges have been approved by the
breaking-change committee. The\n`release_note:breaking` label should be
applied in these situations.\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*`
labels.","sha":"33851e69c204d109a8bae40ef1d7eb03b00f7432"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/233625","number":233625,"mergeCommit":{"message":"apache-arrow:
ensure v20+ (#233625)\n\n## Summary\n\nThe ES client's team needs
apache-arrow to be on v20, at least.\n\nThis PR bumps the ES client's
underlying client to that version by using\n`resolutions` in the
package.json.\n\n### Checklist\n\n- [x] This was checked for breaking
HTTP API changes, and any breaking\nchanges have been approved by the
breaking-change committee. The\n`release_note:breaking` label should be
applied in these situations.\n- [x] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n-
[x] Review the
[backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand
apply applicable `backport:*`
labels.","sha":"33851e69c204d109a8bae40ef1d7eb03b00f7432"}},{"branch":"9.1","label":"v9.1.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/233642","number":233642,"state":"MERGED","mergeCommit":{"sha":"0db04d37e71f86f045d0f4e71b86fdc5e1727a79","message":"[9.1]
apache-arrow: ensure v20+ (#233625) (#233642)\n\n# Backport\n\nThis will
backport the following commits from `main` to `9.1`:\n- [apache-arrow:
ensure
v20+\n(#233625)](https://github.com/elastic/kibana/pull/233625)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Alejandro Fernández Haro
<alejandro.haro@elastic.co>"}},{"branch":"8.19","label":"v8.19.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:version Backport to applied version labels release_note:skip Skip the PR/issue when compiling release notes Team:Core Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t// v8.19.4 v9.1.4 v9.2.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants