Update dependency elasticsearch to v7.17.11 #148
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.
This PR contains the following updates:
"= 7.17.1"
->"= 7.17.11"
Release Notes
elastic/elasticsearch-ruby (elasticsearch)
v7.17.11
Compare Source
base64
dependency toelasticsearch-transport
: base64 was added to the gemspec, since starting in Ruby 3.4.0, base64 will no longer be part of the default gems and will no longer be in the standard library, #2400v7.17.10
Compare Source
Backports support for Faraday 2 from
elastic-transport
. ¡Gracias santiagorodriguez96!This version of the gem now supports Faraday v2. If you don't have a locked version of Faraday in your project, when you upgrade your gems, Faraday v2 will be installed. The main change on dependencies when using Faraday v2 is all adapters, except for the default
net_http
one, have been moved out of Faraday into separate gems. This means if you're not using the default adapter and you migrate to Faraday v2, you'll need to add the adapter gems to your Gemfile.These are the gems required for the different adapters with Faraday 2, instead of the libraries on which they were based:
Things should work fine if you migrate to Faraday 2 as long as you include the adapter (unless you're using the default one
net-http
), but worst case scenario, you can always lock the version of Faraday in your project to 1.x:gem 'faraday', '~> 1'
Be aware if migrating to Faraday v2 that it requires at least Ruby
2.6
, unlike Faraday v1 which requires2.4
.Troubleshooting
If you see a message like:
:adapter is not registered on Faraday::Adapter (Faraday::Error)
Then you probably need to include the adapter library in your gemfile and require it.
Please submit an issue if you encounter any problems.
v7.17.9
Compare Source
elastic-transport
: #66 - Manticore transport unable to send custom headers withperform_request
Pull Request.v7.17.8
Compare Source
v7.17.7
: 7.17.7Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.