Skip to content

feat(elasticsearch): add support for v9 #7180

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 2, 2025
Merged

Conversation

darthf1
Copy link
Contributor

@darthf1 darthf1 commented May 27, 2025

Q A
Branch? main
Tickets N/A
License MIT
Doc PR N/A

https://www.elastic.co/blog/whats-new-elastic-search-9-0-0

Allow Elasticsearch v9

@darthf1 darthf1 changed the title feat(deps): allow Elasticsearch v9 feat(elasticsearch): add support for v9 May 27, 2025
@soyuka
Copy link
Member

soyuka commented May 28, 2025

we should probably force elasticsearch 8 for the v8 ci ?

@darthf1
Copy link
Contributor Author

darthf1 commented May 28, 2025

we should probably force elasticsearch 8 for the v8 ci ?

Yes. Do you know how / have an example where that is done?

@soyuka
Copy link
Member

soyuka commented May 28, 2025

Like https://github.com/api-platform/core/blob/main/.github/workflows/ci.yml#L851 you should use elasticsearch/elasticsearch:8 in the v8 ci as it installs the v9 right now.

@darthf1
Copy link
Contributor Author

darthf1 commented May 28, 2025

Gotcha. Thanks!

@darthf1
Copy link
Contributor Author

darthf1 commented May 29, 2025

Not much I can do about the failing check i guess?

@soyuka soyuka merged commit 24a1cf5 into api-platform:main Jun 2, 2025
97 of 98 checks passed
soyuka pushed a commit that referenced this pull request Jun 2, 2025
@soyuka
Copy link
Member

soyuka commented Jun 2, 2025

thanks! I've actually cherry-picked this on the 4.1 branch as well.

@darthf1 darthf1 deleted the feat/es-9 branch June 2, 2025 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants