Bump Elastic.Clients.Elasticsearch from 8.15.10 to 8.16.3

[dependabot]

Bumps Elastic.Clients.Elasticsearch from 8.15.10 to 8.16.3.

Release notes

Sourced from Elastic.Clients.Elasticsearch's releases.

8.16.3

What's Changed

• Fix RequestConfiguration by @​flobernd in elastic/elasticsearch-net#8426

Full Changelog: elastic/elasticsearch-net@8.16.2...8.16.3

8.16.2

What's Changed

• Update Elastic.Transport to 0.5.6 by @​flobernd in elastic/elasticsearch-net#8422
  • Fixes a NullReferenceException when instrumentation is used

Full Changelog: elastic/elasticsearch-net@8.16.1...8.16.2

8.16.1

What's Changed

• Add API Reference Documentation by @​flobernd in elastic/elasticsearch-net#8228
  • Available here: https://elastic.github.io/elasticsearch-net
• Improve reference documentation by @​flobernd in elastic/elasticsearch-net#8418
• Update Elastic.Transport to 0.5.5 by @​flobernd in elastic/elasticsearch-net#8421

Full Changelog: elastic/elasticsearch-net@8.16.0...8.16.1

8.16.0

What's Changed

• Update TFMs by @​flobernd in elastic/elasticsearch-net#8402
  • Removed net6 target (end of support)
• Update Elastic.Transport to 0.5.2 by @​flobernd in elastic/elasticsearch-net#8405 ( 💥 )
  • Our shared transport library has undergone a major refactoring and is now getting closer to a final release.
  • If you use the low level transport, please check the following changes 0.5.0, 0.5.1, 0.5.2
  • If you do not use the low level transport, you won't experience any breaking change
• Regenerate the client using the latest specification by @​flobernd in elastic/elasticsearch-net#8409
  • TermsQuery.Term property got renamed back to TermsQuery.Terms ( 💥 )
    • This property was accidentally converted to singular with the generator changes starting from 8.13
  • Adds inference APIs
  • Adds IpLocationProcessor
  • Removes deprecated TextExpansionQuery and WeightedTokensQuery ( 💥 )
  • Additional fixes and improvements

Full Changelog: elastic/elasticsearch-net@8.15.10...8.16.0

Commits

• 1e6e472 Fix RequestConfiguration (#8426) (#8428)
• 7240670 Update Elastic.Transport to 0.5.6 (#8422) (#8424)
• 32b828c Add more examples to the documentation (#8374)
• c9cb337 Update Elastic.Transport to 0.5.5 (#8421)
• 21eb7c0 Improve reference documentation (#8418) (#8420)
• aa042ba API Reference Documentation (#8228) (#8417)
• 2b5796f Regenerate the client using the latest specification (#8409) (#8414)
• cbf7635 Update Elastic.Transport to 0.5.2 (#8405) (#8412)
• 808e624 Update TFMs (#8402) (#8413)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

###### Microsoft Reviewers: [Open in CodeFlow](https://microsoft.github.io/open-pr/?codeflow=https://github.com//pull/6952)

[russharding]

FYI, 8.16.x brings breaking changes if you have code that has "advanced" transport layer functionality. For example, ignoring a certificate error for a self-signed SSL cert used in a lower environment.

[eerhardt]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[eerhardt]

FYI, 8.16.x brings breaking changes if you have code that has "advanced" transport layer functionality. For example, ignoring a certificate error for a self-signed SSL cert used in a lower environment.

Do you think this should block taking the update? I see there is now a 8.17.x version out.

[russharding]

FYI, 8.16.x brings breaking changes if you have code that has "advanced" transport layer functionality. For example, ignoring a certificate error for a self-signed SSL cert used in a lower environment.

Do you think this should block taking the update? I see there is now a 8.17.x version out.

No, the update is worth bringing in. My suggestion is that you specifically reference the client documentation so it's clear a possible dependency could bring a breaking change to any adoptions.

I'm not sure how that would impact the versioning of Aspire.

For example, In my project, we have scheduled the update to the Elastic client for next month. So I would be blocked from this Aspire update. The question I can't answer is, how should that be communicated?

[eerhardt]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[eerhardt]

We update to new versions of the underlying client libraries every release. When there are massive breaking changes that don't allow us to span across the version breaking change, we split our package into 2 until the next major version. For example, see RabbitMQ.Client v7 breaks Aspire.RabbitMQ.Client component (dotnet/aspire#3956). This doesn't seem like that kind of breaking change.

I'll add a statement to https://learn.microsoft.com/en-us/dotnet/aspire/fundamentals/integrations-overview that talks about how we update both the docker images and nuget packages to the latest version each release.

UPDATE: Add versioning considerations to integration overview (dotnet/docs-aspire#2425)