Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump Azure.Messaging.EventHubs from 5.10.0 to 5.11.5 in /src/shipping/delivery #59

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 10, 2024

Bumps Azure.Messaging.EventHubs from 5.10.0 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

Dependabot compatibility score

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot added .NET Pull requests that update .net code dependencies Pull requests that update a dependency file labels Sep 10, 2024
@dependabot dependabot bot force-pushed the dependabot/nuget/src/shipping/delivery/Azure.Messaging.EventHubs-5.11.5 branch 2 times, most recently from 7c10e24 to 5b0cf32 Compare September 23, 2024 15:16
Bumps [Azure.Messaging.EventHubs](https://github.com/Azure/azure-sdk-for-net) from 5.10.0 to 5.11.5.
- [Release notes](https://github.com/Azure/azure-sdk-for-net/releases)
- [Commits](Azure/azure-sdk-for-net@Azure.Messaging.EventHubs_5.10.0...Azure.Messaging.EventHubs_5.11.5)

---
updated-dependencies:
- dependency-name: Azure.Messaging.EventHubs
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/nuget/src/shipping/delivery/Azure.Messaging.EventHubs-5.11.5 branch from 5b0cf32 to 5fdb34c Compare September 30, 2024 14:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file .NET Pull requests that update .net code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants