Skip to content

[Snyk] Upgrade @elastic/elasticsearch from 8.13.1 to 9.0.0#7

Open
Dustin4444 wants to merge 1 commit intomainfrom
snyk-upgrade-32995a01680c485a892edc33a2d438a6
Open

[Snyk] Upgrade @elastic/elasticsearch from 8.13.1 to 9.0.0#7
Dustin4444 wants to merge 1 commit intomainfrom
snyk-upgrade-32995a01680c485a892edc33a2d438a6

Conversation

@Dustin4444
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade @elastic/elasticsearch from 8.13.1 to 9.0.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

  • The recommended version is 22 versions ahead of your current version.

  • The recommended version was released a month ago.

Release notes
Package name: @elastic/elasticsearch
  • 9.0.0 - 2025-04-15
  • 9.0.0-alpha.5 - 2025-04-04

    Changes from 9.0.0-alpha.4:

    Serverless client merged back in

    The @ elastic/elasticsearch-serverless client is being deprecated, and its functionality has been merged back into this client. This should have zero impact on the way the client works, except that a new serverMode option has been added. When it's explicitly set to "serverless" by a user, a few default settings and behaviors are changed:

    • turns off sniffing and ignores any sniffing-related options
    • ignores all nodes passed in config except the first one, and ignores any node filtering and selecting options
    • enables compression and TLSv1_2_method (same as when configured for Elastic Cloud)
    • adds an elastic-api-version HTTP header to all requests
    • uses CloudConnectionPool by default instead of WeightedConnectionPool
    • turns off vendored content-type and accept headers in favor or standard MIME types

    Docstrings for types that differ between stack and serverless have also been updated to indicate when that is the case.

  • 9.0.0-alpha.4 - 2025-02-26

    Changes from v9.0.0-alpha.3:

    Parameter collation

    Each API function's logic for deciding where in the request to put each passed parameter is now as follows:

    1. if recognized as a body param from the spec, put it in the JSON body
    2. if recognized as a path param, put it in the URL path
    3. if recognized as a query param or a "common" query param (e.g. pretty, error_trace), put it in the querystring
    4. if not recognized and this API accepts a JSON body, put it in the JSON body
    5. if not recognized and this API does not accept a JSON body, put it in the querystring

    The first two steps are identical to 8.x and prior 9.0.0 alpha releases. The last three steps replace the logic that put all unrecognized params in the querystring.

    Parameter name list management

    Each API function now only instantiates its arrays of accepted body/path/query param names once per client instance rather than during every function call, by moving the array values up to the constructor or module level, depending on which is available. Hopefully this introduces a small performance/memory improvement.

  • 9.0.0-alpha.3 - 2025-01-30

    Changes from 9.0.0-alpha.2:

    • The default 30-second timeout on all HTTP requests sent to Elasticsearch has been dropped in favor of having no timeout set at all. The previous behavior still works as it did when setting the requestTimeout value. #2573
  • 9.0.0-alpha.2 - 2025-01-28

    Changes from 9.0.0-alpha.1:

    • Rather than fully dropping the body parameter, each HTTP request type includes optional body and querystring parameters that will add any provided values to the body and querystring, respectively. They have permissive { [key: string]: any } types (basically Record<string, any>), except they do not allow any of properties that should been in the root of the object.
  • 9.0.0-alpha.1 - 2024-12-05

    This is a 9.0.0 pre-release alpha. Changes may not be stable.

    Breaking changes

    • Drops support for the body parameter from all API calls
  • 8.18.2 - 2025-04-25
  • 8.18.1 - 2025-04-21
  • 8.18.0 - 2025-04-16
  • 8.17.1 - 2025-02-24

    Changelog

  • 8.17.0 - 2024-12-12

    Changelog

  • 8.16.4 - 2025-02-24

    Changelog

  • 8.16.3 - 2024-12-12

    Changelog

  • 8.16.2 - 2024-11-21

    Changelog

  • 8.16.1 - 2024-11-18
  • 8.16.0 - 2024-11-14
  • 8.15.3 - 2024-11-21
  • 8.15.2 - 2024-11-11
  • 8.15.1 - 2024-10-15
  • 8.15.0 - 2024-08-12
  • 8.14.1 - 2024-08-12
  • 8.14.0 - 2024-06-17
  • 8.13.1 - 2024-04-09
from @elastic/elasticsearch GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @elastic/elasticsearch from 8.13.1 to 9.0.0.

See this package in npm:
@elastic/elasticsearch

See this project in Snyk:
https://app.snyk.io/org/dustin4444/project/f27110ea-097b-4515-af2d-df570d85d86c?utm_source=github&utm_medium=referral&page=upgrade-pr
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