Skip to content

chore(deps): update docker.elastic.co/elasticsearch/elasticsearch docker tag to v9 #1111

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

Conversation

elastic-renovate-prod[bot]
Copy link
Contributor

This PR contains the following updates:

Package Update Change
docker.elastic.co/elasticsearch/elasticsearch (source) major 8.18.0 -> 9.0.0

Release Notes

elastic/elasticsearch (docker.elastic.co/elasticsearch/elasticsearch)

v9.0.0: Elasticsearch 9.0.0

Compare Source

Downloads: https://elastic.co/downloads/elasticsearch
Release notes: https://www.elastic.co/docs/release-notes/elasticsearch#elasticsearch-900-release-notes


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@elastic-renovate-prod elastic-renovate-prod bot enabled auto-merge (squash) April 22, 2025 23:28
@elastic-renovate-prod
Copy link
Contributor Author

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

@elastic-renovate-prod elastic-renovate-prod bot merged commit 67daf1e into main Apr 22, 2025
23 checks passed
@elastic-renovate-prod elastic-renovate-prod bot deleted the renovate/docker.elastic.co-elasticsearch-elasticsearch-9.x branch April 22, 2025 23:28
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.

0 participants