[dependabot]

Bumps datamodel-code-generator from 0.31.2 to 0.83.0.

Release notes

Sourced from datamodel-code-generator's releases.

0.83.0

Breaking Changes

Code Generation Changes

• Deduplication now compares referenced models - Models that render identically are only merged when the models they reference also match structurally, so schemas whose same-named references resolve to different definitions in other files no longer collapse into a single class; such models are now emitted separately and may gain suffixed names such as LeafModel or Values1, changing class names and module contents compared with previous output (#4115)
• Generic schemas using $dynamicRef are now specialized per dynamic scope - A plain-name $dynamicRef previously resolved lexically within its own schema resource, so every referrer shared one model of the referenced generic. The parser now tracks the dynamic scope of the schemas that referenced a model, binds each $dynamicAnchor name to its outermost declaration in that scope, and re-parses a referenced schema as an additional specialized model whenever its bindings differ. Schemas that combine $dynamicRef with $dynamicAnchor, including remote, embedded, recursive, root-level and tuple additionalItems generics, now emit extra model classes with suffixed names and different field types than before, so generated module contents, class names and import sites can change for existing users (#4117)
• Specialized dynamic-scope models shift generated class names - Specialized models are registered under the referencing model and named like the shared model before parsing, so the shared model keeps naming priority and specializations receive derived names such as numeric or Model suffixes. Output ordering and names of surrounding models can therefore differ from previous releases, and this applies under --naming-strategy full-path and --collapse-root-models as well (#4117)
• OpenAPI specifications referencing external JSON Schema generics gain specialized models - parse_raw now drains pending dynamic-scope specializations after every specification has been read, so components that reference external schemas rebinding a $dynamicAnchor produce additional specialized models instead of reusing a single shared model (#4117)
• Dynamic ref resolution scope for inline resources and merged refs - $dynamicRef is now resolved within the schema resource a subschema stands for, namely an inline subschema declaring its own $id and the target of a $ref merged with sibling keywords, with enclosing and referencing resources still able to override the binding so the outermost $dynamicAnchor declaration wins; schemas combining $dynamicRef with embedded $id resources or with $ref plus sibling keywords may now generate different field types and model shapes than before, for example a resource-local anchor type such as RootModel[str] where the previous output used the anchor visible in the outer scope (#4119)
• Model reuse no longer merges models whose same-named references point at different models - Deduplication for --reuse-model, --collapse-reuse-models and --reuse-scope=tree previously matched models on rendered output and imports alone, so models that rendered identically but referenced different models sharing a name were incorrectly collapsed into one. Duplicate detection within a module and across modules now also requires the referenced models to match, so these models stay distinct. Affected schemas now generate additional or differently named classes, such as a suffixed FieldModel alongside Field, extra per-module classes, and inheritance from a shared base instead of a single merged model, which can change class names and module layout that downstream code imports (#4121)
• Merged $ref targets now resolve through aliases - A referenced schema that is itself a $ref is merged with its own target, so a $ref with sibling keywords pointing at an alias now generates the aliased definition instead of the alias node, changing model names and field types in generated output for JSON Schema 2020-12 documents that use $ref alongside other keywords (#4122)
• References inside merged targets from other documents are rebased - When a $ref with sibling keywords points into another document, nested $ref and plain-name $dynamicRef values are rewritten to absolute locations before merging, so schemas whose relative references previously resolved against the wrong base now produce different models, imports, and field types (#4122)
• Resolve $recursiveRef in merged cross-document $ref targets - A self-pointing $recursiveRef inside a schema merged in from another document now resolves to the nearest enclosing $recursiveAnchor of its defining document, or that document's root, instead of resolving against the merging document; schemas that rely on the previous resolution generate different recursive model references and field annotations, so regenerated models may name different classes than before, and when the merging document itself declares $recursiveAnchor the reference is instead left to extend the dynamic scope (#4127)
• OpenAPI component schemas that declare an $id are now registered as schema resources - References naming an $id declared inside a component schema now resolve to that embedded schema when the document itself has no matching target, instead of only being treated as document-relative or external document references, and the OpenAPI parser now parses the normalized specification returned by _prepare_schema_resources rather than the original raw specification, so specifications that use $id inside component schemas can produce different models, model names, and field types than before (#4128)
• Merged schema copies now collapse into shared models - Object models parsed from a schema merged in from another document are now recognized as duplicates of an identically named model when their rendered shapes match, even if their dedup keys differ because nested referenced names only converge later in the same pass; schemas that previously produced extra suffixed classes such as a second Tree, Node, or Branch now reuse the single shared model, so generated class names, class counts, and field annotations can change and code importing the previously emitted duplicate class names will need updating (#4133)
• Recursive references inside embedded $id resources resolve to the resource root - A $recursiveRef located in a subschema that declares its own $id but no $recursiveAnchor now targets the root of that embedded resource instead of the nearest enclosing $recursiveAnchor or the document root, both when the document is parsed directly and when its schemas are merged into another document, so affected fields are annotated with the embedded resource model instead of the outer model, and targets reachable only through $recursiveRef are now loaded and can add generated models (#4130)
• Root models of documents referenced only by JSON pointer are named after the document - When an external document is reached only through pointer references into it and its own subschemas refer back to the document root, that root model was previously generated as Field or FieldModel; it is now named after the file stem, for example Tree or Node, so class names and field annotations such as list[Field] change for such schemas (#4132)

Error Handling Changes

• New warning for allOf base classes that cannot follow dynamic scope bindings - When an allOf base class is referenced from a schema whose dynamic scope would rebind its $dynamicAnchor, the parser now emits a UserWarning stating that the base class resolves its $dynamicRef within its own schema resources. Generation still succeeds, but builds that treat warnings as errors or assert on captured warnings can now fail (#4117)
• New SchemaResourceRefWarning raised for compatibility-resolved references - A reference that keeps resolving against the document, or keeps loading the referenced document, for compatibility while JSON Schema would resolve it to an embedded $id resource now emits the newly added SchemaResourceRefWarning, so generation runs that previously completed silently can now surface warnings and can fail where warnings are configured as errors (#4128)

Default Behavior Changes

• External reference mapping keys are matched against the defining document - Because merged target references are rebased to absolute locations, --external-ref-mapping entries must now name the path of the document the reference actually comes from rather than a path relative to the merged target, so existing mappings that relied on the previous matching may silently stop applying (#4122)

What's Changed

• Rebalance CI test shard weights by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4085
• Run measured slow tests first by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4086
• Balance Windows and macOS test shards by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4087
• Fix release draft validation for stacked pull requests by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4088
• Record per-version CI test shard weights by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4089
• Add Ubuntu coverage test shards by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4090
• Run payload validation only with coverage by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4092
• Bump the github-actions group with 7 updates by @​dependabot[bot] in datamodel-code-generator/datamodel-code-generator#4096
• [pre-commit.ci] pre-commit autoupdate by @​pre-commit-ci[bot] in datamodel-code-generator/datamodel-code-generator#4067
• Add generation observation baselines by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4099
• Add parser generation factories by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4100
• Share generation attempt lifecycle by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4101
• Add canonical API declaration references by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4103
• Add explicit OpenAPI API scope by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4104
• Verify API scope generation contracts by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4105
• Add TypeSafe Jev SDK usage example by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4134
• Fix merging models with different referenced types by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4115
• Fix plain-name $dynamicRef in embedded schema resources by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4116
• Fix $dynamicRef generics losing dynamic scope bindings by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4117
• Fix $dynamicRef scope in inline schema resources by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4119
• Fix tree-scope reuse leaving references to removed duplicates by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4120
• Fix model reuse merging models with different referenced types by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4121

... (truncated)

Changelog

Sourced from datamodel-code-generator's changelog.

0.83.0 - 2026-09-24

Breaking Changes

Code Generation Changes

• Deduplication now compares referenced models - Models that render identically are only merged when the models they reference also match structurally, so schemas whose same-named references resolve to different definitions in other files no longer collapse into a single class; such models are now emitted separately and may gain suffixed names such as LeafModel or Values1, changing class names and module contents compared with previous output (#4115)
• Generic schemas using $dynamicRef are now specialized per dynamic scope - A plain-name $dynamicRef previously resolved lexically within its own schema resource, so every referrer shared one model of the referenced generic. The parser now tracks the dynamic scope of the schemas that referenced a model, binds each $dynamicAnchor name to its outermost declaration in that scope, and re-parses a referenced schema as an additional specialized model whenever its bindings differ. Schemas that combine $dynamicRef with $dynamicAnchor, including remote, embedded, recursive, root-level and tuple additionalItems generics, now emit extra model classes with suffixed names and different field types than before, so generated module contents, class names and import sites can change for existing users (#4117)
• Specialized dynamic-scope models shift generated class names - Specialized models are registered under the referencing model and named like the shared model before parsing, so the shared model keeps naming priority and specializations receive derived names such as numeric or Model suffixes. Output ordering and names of surrounding models can therefore differ from previous releases, and this applies under --naming-strategy full-path and --collapse-root-models as well (#4117)
• OpenAPI specifications referencing external JSON Schema generics gain specialized models - parse_raw now drains pending dynamic-scope specializations after every specification has been read, so components that reference external schemas rebinding a $dynamicAnchor produce additional specialized models instead of reusing a single shared model (#4117)
• Dynamic ref resolution scope for inline resources and merged refs - $dynamicRef is now resolved within the schema resource a subschema stands for, namely an inline subschema declaring its own $id and the target of a $ref merged with sibling keywords, with enclosing and referencing resources still able to override the binding so the outermost $dynamicAnchor declaration wins; schemas combining $dynamicRef with embedded $id resources or with $ref plus sibling keywords may now generate different field types and model shapes than before, for example a resource-local anchor type such as RootModel[str] where the previous output used the anchor visible in the outer scope (#4119)
• Model reuse no longer merges models whose same-named references point at different models - Deduplication for --reuse-model, --collapse-reuse-models and --reuse-scope=tree previously matched models on rendered output and imports alone, so models that rendered identically but referenced different models sharing a name were incorrectly collapsed into one. Duplicate detection within a module and across modules now also requires the referenced models to match, so these models stay distinct. Affected schemas now generate additional or differently named classes, such as a suffixed FieldModel alongside Field, extra per-module classes, and inheritance from a shared base instead of a single merged model, which can change class names and module layout that downstream code imports (#4121)
• Merged $ref targets now resolve through aliases - A referenced schema that is itself a $ref is merged with its own target, so a $ref with sibling keywords pointing at an alias now generates the aliased definition instead of the alias node, changing model names and field types in generated output for JSON Schema 2020-12 documents that use $ref alongside other keywords (#4122)
• References inside merged targets from other documents are rebased - When a $ref with sibling keywords points into another document, nested $ref and plain-name $dynamicRef values are rewritten to absolute locations before merging, so schemas whose relative references previously resolved against the wrong base now produce different models, imports, and field types (#4122)
• Resolve $recursiveRef in merged cross-document $ref targets - A self-pointing $recursiveRef inside a schema merged in from another document now resolves to the nearest enclosing $recursiveAnchor of its defining document, or that document's root, instead of resolving against the merging document; schemas that rely on the previous resolution generate different recursive model references and field annotations, so regenerated models may name different classes than before, and when the merging document itself declares $recursiveAnchor the reference is instead left to extend the dynamic scope (#4127)
• OpenAPI component schemas that declare an $id are now registered as schema resources - References naming an $id declared inside a component schema now resolve to that embedded schema when the document itself has no matching target, instead of only being treated as document-relative or external document references, and the OpenAPI parser now parses the normalized specification returned by _prepare_schema_resources rather than the original raw specification, so specifications that use $id inside component schemas can produce different models, model names, and field types than before (#4128)
• Merged schema copies now collapse into shared models - Object models parsed from a schema merged in from another document are now recognized as duplicates of an identically named model when their rendered shapes match, even if their dedup keys differ because nested referenced names only converge later in the same pass; schemas that previously produced extra suffixed classes such as a second Tree, Node, or Branch now reuse the single shared model, so generated class names, class counts, and field annotations can change and code importing the previously emitted duplicate class names will need updating (#4133)
• Recursive references inside embedded $id resources resolve to the resource root - A $recursiveRef located in a subschema that declares its own $id but no $recursiveAnchor now targets the root of that embedded resource instead of the nearest enclosing $recursiveAnchor or the document root, both when the document is parsed directly and when its schemas are merged into another document, so affected fields are annotated with the embedded resource model instead of the outer model, and targets reachable only through $recursiveRef are now loaded and can add generated models (#4130)
• Root models of documents referenced only by JSON pointer are named after the document - When an external document is reached only through pointer references into it and its own subschemas refer back to the document root, that root model was previously generated as Field or FieldModel; it is now named after the file stem, for example Tree or Node, so class names and field annotations such as list[Field] change for such schemas (#4132)

Error Handling Changes

• New warning for allOf base classes that cannot follow dynamic scope bindings - When an allOf base class is referenced from a schema whose dynamic scope would rebind its $dynamicAnchor, the parser now emits a UserWarning stating that the base class resolves its $dynamicRef within its own schema resources. Generation still succeeds, but builds that treat warnings as errors or assert on captured warnings can now fail (#4117)
• New SchemaResourceRefWarning raised for compatibility-resolved references - A reference that keeps resolving against the document, or keeps loading the referenced document, for compatibility while JSON Schema would resolve it to an embedded $id resource now emits the newly added SchemaResourceRefWarning, so generation runs that previously completed silently can now surface warnings and can fail where warnings are configured as errors (#4128)

Default Behavior Changes

• External reference mapping keys are matched against the defining document - Because merged target references are rebased to absolute locations, --external-ref-mapping entries must now name the path of the document the reference actually comes from rather than a path relative to the merged target, so existing mappings that relied on the previous matching may silently stop applying (#4122)

What's Changed

• Rebalance CI test shard weights by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4085
• Run measured slow tests first by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4086
• Balance Windows and macOS test shards by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4087
• Fix release draft validation for stacked pull requests by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4088
• Record per-version CI test shard weights by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4089
• Add Ubuntu coverage test shards by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4090
• Run payload validation only with coverage by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4092
• Bump the github-actions group with 7 updates by @​dependabot[bot] in datamodel-code-generator/datamodel-code-generator#4096
• [pre-commit.ci] pre-commit autoupdate by @​pre-commit-ci[bot] in datamodel-code-generator/datamodel-code-generator#4067
• Add generation observation baselines by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4099
• Add parser generation factories by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4100
• Share generation attempt lifecycle by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4101
• Add canonical API declaration references by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4103
• Add explicit OpenAPI API scope by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4104
• Verify API scope generation contracts by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4105
• Add TypeSafe Jev SDK usage example by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4134
• Fix merging models with different referenced types by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4115
• Fix plain-name $dynamicRef in embedded schema resources by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4116
• Fix $dynamicRef generics losing dynamic scope bindings by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4117
• Fix $dynamicRef scope in inline schema resources by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4119
• Fix tree-scope reuse leaving references to removed duplicates by @​koxudaxi in datamodel-code-generator/datamodel-code-generator#4120

... (truncated)

Commits

• f59ac9f docs: update release benchmark data (#4082)
• 0fdffc7 Fix release draft breaking changes merge (#4138)
• 3e2b6d8 Switch release draft analysis to Opus 5.5 (#4137)
• 5acbd12 [pre-commit.ci] pre-commit autoupdate (#4113)
• ad26676 Fix duplicate models left by merged copies of recursive schemas (#4133)
• 01df579 Fix Field class name for roots of pointer-referenced documents (#4132)
• 352362f Fix $anchor references in OpenAPI component schemas (#4131)
• 066dff1 Fix $recursiveRef targets in embedded $id resources and other documents (#4130)
• 3532c44 Fix $ref to embedded $id resources in OpenAPI component schemas (#4128)
• 1fa694f Fix $recursiveRef in cross-file merged $ref targets (#4127)
• Additional commits viewable in compare view

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 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]

Superseded by #959.