chore(deps): update all non-major dependencies #1
Loading…
Reference in New Issue
No description provided.
Delete Branch "renovate/all-minor-patch"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
3.18
->3.19
'>= 7', '< 7.14'
->'>= 7', '< 7.17.11'
"~> 5.2.5"
->"~> 5.4.0"
"~> 3.2.0"
->"~> 3.4.0"
"~> 1.0.0"
->"~> 1.1.0"
"~> 2.1.0"
->"~> 2.2.0"
"1.16.3"
->"1.16.5"
"~> 3.15.0"
->"~> 3.16.0"
Release Notes
elastic/elasticsearch-ruby (elasticsearch)
v7.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
v7.17.1
: 7.17.1Compare Source
safe_load
instead ofload
when doing the product verification (should only affect Ruby < 3.0).v7.17.0
: 7.17.0Compare Source
413
error.v7.16.3
: 7.16.3Compare Source
API
Bugfix for #1475, an issue where if you indexed a document with an id such as
an id
, it would get escaped toan+id
instead ofan%20id
when usingindex
orcreate
. This would result in the document id beingan+id
instead of the intended valuean id
.v7.16.1
Compare Source
Patch release corresponding with Elastic Stack version 7.16.1 that addresses the Apache Log4j2 vulnerability, more information.
Client
The only changes in the client since 7.16.0 are a few minor updates for the Compatibility mode with 8.0. We added the compatibility header in
7.13.0
, but now we have integration tests and compatibility tests for version7.x
of the client with Elasticsearch8.0
.v7.16.0
: 7.16.0Compare Source
7.16.0
Client
delay_on_retry
parameter, a value in milliseconds to wait between each failed connection, thanks DinoPullerUqido! Pull Request and backport.ca_fingerprint
option. This will verify that the fingerprint of the CA certificate that has signed the certificate of the server matches the supplied value:The verification will be run once per connection.
compression
is set totrue
, the client will now gzip the request body properly and use the appropiate headers. Thanks johnnyshields! Pull Request and backport.API
Updates
count
- The API is documented as usingGET
, but it supports both GET and POST on the Elasticsearch side. So it was updated to only usePOST
when there's a body present, or else useGET
. Elasticsearch would still accept a body withGET
, but to be more semantically correct in the clients we usePOST
when there's a body.delete_index_template
was updated to support theignore_404
parameter to ignore 404 errors when attempting to delete a non-existing template.ingest.put_pipeline
adds new parameterif_version
: Required version for optimistic concurrency control for pipeline updates.ml.put_trained_model
: adds new parameterdefer_definition_decompression
: If set totrue
and acompressed_definition
is provided, the request defers definition decompression and skips relevant validations.nodes.hot_threads
adds new parametersort
: The sort order for 'cpu' type (default: total) (options: cpu, total).open_point_in_time
:keep_alive
is now a required parameter.search_mvt
: adds new parametertrack_total_hits
: Indicate if the number of documents that match the query should be tracked. A number can also be specified, to accurately track the total hit count up to the number.transform.preview_transform
: adds new parametertransform_id
. Body is now optional and the API will useGET
orPOST
depending on the presence of a body.APIs promoted from experimental to stable since last version:
fleet.global_checkpoints
get_script_context
get_script_language
indices.resolve_index
monitoring.bulk
rank_eval
searchable_snapshots.mount
searchable_snapshots.stats
security.clear_cached_service_tokens
security.create_service_token
security.delete_service_token
security.get_service_accounts
security.get_service_credentials
shutdown.delete_node
shutdown.get_node
shutdown.put_node
terms_enum
New APIs
fleet.mseach
fleet.search
indices.modify_data_stream
ml.infer_trained_model_deployment
ml.start_trained_model_deployment
ml.stop_trained_model_deployment
migration.get_feature_upgrade_status
migration.post_feature_upgrade_status
security.enroll_kibana
security.enroll_node
transform.updgrade_transforms
v7.15.0
: 7.15.0Compare Source
7.15.0
Client
API
indices.disk_usage
.indices.field_usage_stats
,nodes.clear_repositories_metering_archive
,get_repositories_metering_info
,search_mvt
index
parameter is now required foropen_point_in_time
.index_metric
parameter innodes.stats
adds theshards
option.X-Pack
ml.put_job
:ignore_unavailable
,allow_no_indices
,ignore_throttled
,expand_wildcards
.security.query_api_keys
.v7.14.1
: 7.14.1Compare Source
Client
3732dd4f6d
) and fixes tracing (3c48ebd9a7
). Related to #1426 and #1428.v7.14.0
: 7.14.0Compare Source
Client
Added check that client is connected to an Elasticsearch cluster. If the client isn't connected to a supported Elasticsearch cluster the
UnsupportedProductError
exception will be raised.This release changes the way in which the transport layer and the client interact. Previously, when using
elasticsearch-transport
,Elasticsearch::Transport::Client
had a convenient wrapper, so it could be used asElasticsearch::Client
. Now, we are decoupling the transport layer from the Elasticsearch client. If you're using theelasticsearch
gem, not much will change. It will instantiate a newElasticsearch::Transport::Client
when you instantiateElasticsearch::Client
and the endpoints fromelasticsearch-api
will be available.Elasticsearch::Client
has anattr_accessor
for the transport instance:The interaction with
elasticsearch-api
remains unchanged. You can use the API endpoints just like before:Or perform request directly from the client which will return an
Elasticsearch::Transport::Response
object:If you have any problems, please report them in this issue.
API
Code is now generated from Elastic artifacts instead of checked out code of Elasticsearch. See the Generator README for more info.
msearch
,msearch_template
andsearch_template
removequery_and_fetch
anddfs_query_and_fetch
options from thesearch_type
parameter.include_repository
insnapshot.get
: (boolean) Whether to include the repository name in the snapshot info. Defaults to true.X-Pack
X-Pack is being deprecated. The first time using
xpack
on the client, a warning will be triggered. Please check this issue for more information.index_lifecycle_management.migrate_to_data_tiers
,machine_learning.reset_job
,security.saml_authenticate
,security.saml_complete_logout
,security.saml_invalidate
,security.saml_logout
,security.saml_prepare_authentication
,security.saml_service_provider_metadata
,sql.delete_async
,sql.get_async
,sql.get_async_status
,terms_enum
.machine_learning.infer_trained_model_deployment
,machine_learning.start_trained_model_deployment
,machine_learning.stop_trained_model_deployment
.indices.freeze
andindices.unfreeze
: Frozen indices are deprecated because they provide no benefit given improvements in heap memory utilization. They will be removed in a future release.uken/fluent-plugin-elasticsearch (fluent-plugin-elasticsearch)
v5.4.3
Compare Source
v5.4.2
Compare Source
v5.4.1
Compare Source
v5.4.0
Compare Source
v5.3.0
Compare Source
faraday
from v1, upgrade to v2. (#1012)Note that if you can't migrate other plugins from
faraday
v1 yet, need to keepfluent-plugin-elasticsearch v5.2.5.
fabric8io/fluent-plugin-kubernetes_metadata_filter (fluent-plugin-kubernetes_metadata_filter)
v3.4.0
Compare Source
v3.3.0
Compare Source
repeatedly/fluent-plugin-multi-format-parser (fluent-plugin-multi-format-parser)
v1.1.0
Compare Source
repeatedly/fluent-plugin-record-modifier (fluent-plugin-record-modifier)
v2.2.0
Compare Source
ohler55/oj (oj)
v3.16.3
Compare Source
v3.16.2
Compare Source
Fixed documentation formatting.
Added option to the "usual" parser to raise an error on an empty input string.
v3.16.1
Compare Source
v3.16.0
Compare Source
Added the
float_format
option.Expanded the
max_nesting
option to allow integer values as well asthe previous boolean (true or nil).
Skip nesting tests with Truffle Ruby in the json gem tests.
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.
9d69bfd807
tob4fc6d9764
b4fc6d9764
toa342dc2e4a
a342dc2e4a
to7bda02d63f