Bump Azure.Messaging.EventHubs from 5.11.3 to 5.11.5 in /src

[dependabot]

Bumps Azure.Messaging.EventHubs from 5.11.3 to 5.11.5.

Release notes

Sourced from Azure.Messaging.EventHubs's releases.

Azure.Messaging.EventHubs.Processor_5.11.5

5.11.5 (2024-08-14)

Other Changes

• Bump Azure.Core.Amqp dependency to 1.3.1, which includes a fix to serialization of binary application properties.

Azure.Messaging.EventHubs_5.11.5

5.11.5 (2024-07-31)

Other Changes

• Bump Azure.Core.Amqp dependency to 1.3.1, which includes a fix to serialization of binary application properties.

Azure.Messaging.EventHubs.Processor_5.11.4

5.11.4 (2024-07-17)

Bugs Fixed

• Fixed an error that prevented relative URIs from being used with application properties in the EventData.Properties collection.

• Fixed an error with ETW logs which caused structured arguments for Id 105 (Event Processor position determined) to be out-of-order with the message format. This also caused the date to render incorrectly for some captures.

Other Changes

• The processor will now refresh the maximum message size each time a new AMQP link is opened; this is necessary for large message support, where the maximum message size for entities can be reconfigured and adjusted on the fly. Because the client had cached the value, it would not be aware of the change and would enforce the wrong size for batch creation.

• Adjusted the options used by the processor during startup validation to reduce the amount of data transferred and minimize impact on the outgoing events metric.

Azure.Messaging.EventHubs_5.11.4

5.11.4 (2024-07-17)

Bugs Fixed

• Fixed an error that prevented relative URIs from being used with application properties in the EventData.Properties collection.

• Fixed an error with ETW logs which caused structured arguments for Id 105 (Event Processor position determined) to be out-of-order with the message format. This also caused the date to render incorrectly for some captures.

Other Changes

• The client will now refresh the maximum message size each time a new AMQP link is opened; this is necessary for large message support, where the maximum message size for entities can be reconfigured and adjusted on the fly. Because the client had cached the value, it would not be aware of the change and would enforce the wrong size for batch creation.

• The PluggableCheckpointStoreEventProcessor will now emit a diagnostic span when a checkpoint is created/updated. While this span is not defined by the Open Telemetry specification, this change aligns diagnostic spans with those emitted by EventProcessorClient.

• Adjusted the options used by EventProcessor<TPartition> and descendants during startup validation to reduce the amount of data transferred and minimize impact on the outgoing events metric.

Commits

• 32a40b6 Prepare for release (#45279)
• b33fbe8 Update AutoRest C# version to 3.0.0-beta.20240730.1 (#45276)
• dddaee0 exclude batch track1 tools folder from doc-warden (#45250)
• 8925600 Update 1.4.0 release note for Azure.Messaging.WebPubSub (#45274)
• 3e6be80 Increment package version after release of Microsoft.Azure.WebJobs.Extensions...
• d6c1aaf Prepare for release (#45269)
• 479a6dc Update dependency version (#45264)
• 705c1d5 Add silent auth sample to TokenCache.md (#45263)
• 2030bb1 update the entry to catch git config errors before the push happens (#45262)
• d27b710 Prepare for release (#45260)
• Additional commits viewable 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)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.27%. Comparing base (183fb57) to head (07499a7).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3211   +/-   ##
=======================================
  Coverage   83.27%   83.27%           
=======================================
  Files         327      327           
  Lines       12422    12422           
  Branches      980      980           
=======================================
  Hits        10344    10344           
  Misses       1785     1785           
  Partials      293      293           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.