Skip to content

Update elasticsearch-rest-client, ... to 8.19.18 in series/8.x#4013

Merged
Philippus merged 1 commit into
Philippus:series/8.xfrom
scala-steward:update/series/8.x/elasticsearch-rest-client-8.19.18
Jul 4, 2026
Merged

Update elasticsearch-rest-client, ... to 8.19.18 in series/8.x#4013
Philippus merged 1 commit into
Philippus:series/8.xfrom
scala-steward:update/series/8.x/elasticsearch-rest-client-8.19.18

Conversation

@scala-steward

Copy link
Copy Markdown
Contributor

About this PR

📦 Updates

from 8.19.17 to 8.19.18

📜 GitHub Release Notes - Version Diff

Usage

Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

🔍 Files still referring to the old version number

The following files still refer to the old version number (8.19.17).
You might want to review and update them manually.

.github/actions/launch-elasticsearch/action.yml
docker-compose.yml
⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.elasticsearch.client" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.elasticsearch.client" }
}]
labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

@Philippus Philippus force-pushed the update/series/8.x/elasticsearch-rest-client-8.19.18 branch from 3aeaa82 to 49e5215 Compare July 4, 2026 10:04
@Philippus Philippus merged commit d4a1cb1 into Philippus:series/8.x Jul 4, 2026
4 checks passed
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