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.Processor, Azure.Messaging.EventHubs and Azure.Storage.Blobs in /src #3184

Merged
merged 1 commit into from
Aug 23, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 22, 2024

Bumps Azure.Messaging.EventHubs.Processor, Azure.Messaging.EventHubs and Azure.Storage.Blobs. These dependencies needed to be updated together.
Updates Azure.Messaging.EventHubs.Processor from 5.11.3 to 5.11.5

Release notes

Sourced from Azure.Messaging.EventHubs.Processor'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.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.

Commits

Updates 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

Updates Azure.Storage.Blobs from 12.20.0 to 12.21.1

Release notes

Sourced from Azure.Storage.Blobs's releases.

Azure.Storage.Blobs_12.21.1

12.21.1 (2024-07-25)

Bugs Fixed

  • Fixed [BUG] Azure Blob Storage Client SDK No Longer Supports Globalization Invariant Mode for Account Key Authentication #45052

Azure.Storage.Blobs_12.21.0

12.21.0 (2024-07-16)

Features Added

  • Includes all features from 12.21.0-beta.1.

Bugs Fixed

  • Fixed bug where storage clients when constructed with URLs with '#' character would truncate the blob name at the '#'.
Commits

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)

@dependabot dependabot bot requested a review from a team as a code owner August 22, 2024 14:00
@dependabot dependabot bot added .NET Pull requests that update .net code dependencies Pull requests that update a dependency file labels Aug 22, 2024
Copy link

codecov bot commented Aug 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.04%. Comparing base (a5b4b74) to head (f5faae2).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3184   +/-   ##
=======================================
  Coverage   86.04%   86.04%           
=======================================
  Files         295      295           
  Lines       11331    11331           
  Branches      873      873           
=======================================
  Hits         9750     9750           
  Misses       1298     1298           
  Partials      283      283           

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

@Metal-Mighty Metal-Mighty enabled auto-merge (rebase) August 22, 2024 15:13
@Metal-Mighty Metal-Mighty force-pushed the dependabot/nuget/src/multi-f40070c487 branch 2 times, most recently from 8fd936a to daf6e6a Compare August 23, 2024 08:06
…nd Azure.Storage.Blobs

Bumps [Azure.Messaging.EventHubs.Processor](https://github.com/Azure/azure-sdk-for-net), [Azure.Messaging.EventHubs](https://github.com/Azure/azure-sdk-for-net) and [Azure.Storage.Blobs](https://github.com/Azure/azure-sdk-for-net). These dependencies needed to be updated together.

Updates `Azure.Messaging.EventHubs.Processor` from 5.11.3 to 5.11.5
- [Release notes](https://github.com/Azure/azure-sdk-for-net/releases)
- [Commits](Azure/azure-sdk-for-net@Azure.Messaging.EventHubs.Processor_5.11.3...Azure.Messaging.EventHubs.Processor_5.11.5)

Updates `Azure.Messaging.EventHubs` from 5.11.3 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.11.3...Azure.Messaging.EventHubs_5.11.5)

Updates `Azure.Storage.Blobs` from 12.20.0 to 12.21.1
- [Release notes](https://github.com/Azure/azure-sdk-for-net/releases)
- [Commits](Azure/azure-sdk-for-net@Azure.Storage.Blobs_12.20.0...Azure.Storage.Blobs_12.21.1)

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

Signed-off-by: dependabot[bot] <support@github.com>
@Metal-Mighty Metal-Mighty force-pushed the dependabot/nuget/src/multi-f40070c487 branch from daf6e6a to f5faae2 Compare August 23, 2024 08:06
@Metal-Mighty Metal-Mighty merged commit 721e9f7 into main Aug 23, 2024
6 checks passed
@Metal-Mighty Metal-Mighty deleted the dependabot/nuget/src/multi-f40070c487 branch August 23, 2024 08:14
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.

1 participant