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 Cosmos SDK to 3.46.0 #35171

Merged
merged 1 commit into from
Nov 21, 2024
Merged

Bump Cosmos SDK to 3.46.0 #35171

merged 1 commit into from
Nov 21, 2024

Conversation

roji
Copy link
Member

@roji roji commented Nov 21, 2024

The new SDK is notably needed to use the new Linux-based Cosmos emulator.

@roji roji requested a review from a team November 21, 2024 13:24
@roji roji enabled auto-merge (squash) November 21, 2024 13:25
@roji
Copy link
Member Author

roji commented Nov 21, 2024

Cosmos SDK now wants its users to reference Newtonsoft.JSON themselves (issue). Following the same logic, I think our provider shouldn't reference it, but our tests will need to (hopefully that's going to work).

@roji
Copy link
Member Author

roji commented Nov 21, 2024

OK, looks like we have to reference Newtonsoft.JSON anyway, since we use Newtonsoft in our own code (in the provider itself). If we one day stop doing that, we'd have the question of whether we should reference Newtonsoft.JSON at all here, or set AzureCosmosDisableNewtonsoftJsonCheck to true (but at that point, I'm not sure if applications using our provider get the build error telling them to reference Newtonsoft.JSON).

@roji roji merged commit 3f5dcef into dotnet:main Nov 21, 2024
7 checks passed
@roji roji deleted the CosmosSdk branch November 21, 2024 19:18
@AndriySvyryd
Copy link
Member

#14570 #34567 #17306

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants