Document Cosmos JSON breaking changes for EF Core 11 - #5432
Merged
cincuranet merged 4 commits intoJul 30, 2026
Conversation
Copilot
AI
changed the title
Document Cosmos JSON breaking changes
Document Cosmos JSON breaking changes for EF Core 11
Jul 28, 2026
Copilot created this pull request from a session on behalf of
AndriySvyryd
July 28, 2026 00:26
View session
Contributor
There was a problem hiding this comment.
Pull request overview
Documents EF Core 11 breaking changes for the Azure Cosmos DB provider related to switching the internal JSON materializer from Newtonsoft.Json/JObject to System.Text.Json, including the removal of __jObject and the loss of unmapped-property round-tripping.
Changes:
- Adds new high-impact breaking change entries covering
__jObjectremoval and unmapped property loss, plus a low-impact note on numeric truncation behavior. - Updates EF Core 11 “What’s New” with a Cosmos section describing the modernized JSON serializer and pointing to the breaking changes.
- Updates Cosmos provider “unstructured data” docs to clarify
__jObjectis removed in EF Core 11 and link to the breaking change.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| entity-framework/core/what-is-new/ef-core-11.0/whatsnew.md | Adds a Cosmos “Modernized JSON serializer” section and links to breaking changes. |
| entity-framework/core/what-is-new/ef-core-11.0/breaking-changes.md | Adds new Cosmos breaking change entries (high + low impact) and mitigations. |
| entity-framework/core/providers/cosmos/unstructured-data.md | Updates __jObject guidance for EF Core 11 and links to the breaking changes. |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
cincuranet
approved these changes
Jul 30, 2026
Contributor
|
@copilot resolve the merge conflicts in this pull request |
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
EF Core 11 (dotnet/efcore#38550) replaces
Newtonsoft.Json/JObjectwithSystem.Text.Jsonin the Cosmos materializer, removing__jObjectand dropping unmapped property preservation.Breaking changes documented (
breaking-changes.md)New High-impact changes section added before the existing Medium-impact section:
__jObjectshadow property removed —JObjectno longer exists on entities; accessing it throws. Mitigation: useCosmosClientdirectly to read raw JSON.CosmosClient.New Low-impact entry added:
int,decimal, etc.) are now truncated instead of rounded, fixing dotnet/efcore#38138.What's new (
whatsnew.md)Added Modernized JSON serializer section to the Cosmos DB area noting the switch to
System.Text.Jsonand linking to the breaking changes.Provider docs (
unstructured-data.md)Updated the
__jObjectsection to reflect that the property is gone in EF Core 11, with a link to the breaking change entry.