8000 Bumped Azurite version to 3.33.0 by Thovenaar · Pull Request #6670 · dotnet/aspire · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Bumped Azurite version to 3.33.0 #6670

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

Merged
merged 2 commits into from
Nov 14, 2024
Merged

Conversation

Thovenaar
Copy link
Contributor
@Thovenaar Thovenaar commented Nov 14, 2024

Description

Fixes the following exception when starting an Azure Storage container with .NET 9 packages installed.

"Azure.RequestFailedException: The API version 2025-01-05 is not supported by Azurite. Please upgrade Azurite to latest version and retry."

Checklist

  • Is this feature complete?
    • Yes. Ready to ship.
    • No. Follow-up changes expected.
  • Are you including unit tests for the changes and scenario tests if relevant?
    • Yes
    • No
  • Did you add public API?
    • Yes
      • If yes, did you have an API Review for it?
        • Yes
        • No
      • Did you add <remarks /> and <code /> elements on your triple slash comments?
        • Yes
        • No
    • No
  • Does the change make any security assumptions or guarantees?
    • Yes
      • If yes, have you done a threat model and had a security review?
        • Ye 8000 s
        • No
    • No
  • Does the change require an update in our Aspire docs?
Microsoft Reviewers: Open in CodeFlow

@dotnet-policy-service dotnet-policy-service bot added the community-contribution Indicates that the PR has been added by a community member label Nov 14, 2024
@eerhardt
Copy link
Member

I'd like to understand how you got this exception better. Did you explicitly update Azure.Storage.Blobs to 12.23.0? The Aspire.Azure.Storage.Blobs package references 12.22.2, which doesn't know about 2025-01-05.

Typically we update the container version and the client integration version at the same time. Can you also update

<PackageVersion Include="Azure.Storage.Blobs" Version="12.22.2" />
<PackageVersion Include="Azure.Storage.Queues" Version="12.20.1" />

as well?

@Thovenaar
Copy link
Contributor Author

I'd like to understand how you got this exception better. Did you explicitly update Azure.Storage.Blobs to 12.23.0? The Aspire.Azure.Storage.Blobs package references 12.22.2, which doesn't know about 2025-01-05.

Typically we update the container version and the client integration version at the same time. Can you also update

<PackageVersion Include="Azure.Storage.Blobs" Version="12.22.2" />
<PackageVersion Include="Azure.Storage.Queues" Version="12.20.1" />

as well?

I am not completely sure which package upgrade caused the issue, since it started happening after everything was upgraded to the latest version. However, both packages you mentioned are on the latest version on our side.

@Thovenaar
Copy link
Contributor Author

@dotnet-policy-service agree

Copy link
Member
@eerhardt eerhardt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks for the contribution!

@eerhardt eerhardt enabled auto-merge (squash) November 14, 2024 21:13
@eerhardt eerhardt merged commit 10e511f into dotnet:main Nov 14, 2024
9 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Dec 16, 2024
@Thovenaar Thovenaar deleted the azurite-version-bump branch March 1, 2025 12:58
@github-actions github-actions bot added the area-integrations Issues pertaining to Aspire Integrations packages label Mar 10, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-integrations Issues pertaining to Aspire Integrations packages community-contribution Indicates that the PR has been added by a community member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0