Bump datamodel-code-generator from 0.71.0 to 0.74.0

[dependabot]

Bumps datamodel-code-generator from 0.71.0 to 0.74.0.

Release notes

Sourced from datamodel-code-generator's releases.

0.74.0

Breaking Changes

Code Generation Changes

• Non-finite float values now render as structural float(...) expressions - Generated code for non-finite floats (inf, -inf, nan) from Protocol Buffers, XML Schema, and AsyncAPI-embedded schemas — as field defaults, constraint bounds, list items, and enum values — now renders inline as float('inf'), float('-inf'), and float('nan') instead of emitting bare inf/nan literals with an injected from math import inf, nan header. Users relying on the previous output (e.g. snapshot/golden tests, or importing inf/nan from the generated module) will see different generated code (#3770)

# Before
from math import inf
class Model(BaseModel):
value: float | None = inf
After
class Model(BaseModel):
value: float | None = float('inf')

What's Changed

• Update CHANGELOG for 0.73.0 by @​dcg-generated-docs[bot] in koxudaxi/datamodel-code-generator#3767
• Update release benchmark data by @​dcg-generated-docs[bot] in koxudaxi/datamodel-code-generator#3768
• Deploy release benchmark data updates by @​koxudaxi in koxudaxi/datamodel-code-generator#3771
• fix(parser): render non-finite values structurally by @​Aryan-Pardeshi in koxudaxi/datamodel-code-generator#3770

New Contributors

• @​Aryan-Pardeshi made their first contribution in koxudaxi/datamodel-code-generator#3770

Full Changelog: koxudaxi/datamodel-code-generator@0.73.0...0.74.0

0.73.0

Breaking Changes

Error Handling Changes

• Additional imports are now validated as Python import paths - Values passed via --additional-imports, the Python config API (GenerateConfig, JSONSchemaParserConfig, etc.), or --extra-template-data must now be dotted sequences of Python identifiers. Previously any value was accepted and split on commas without validation; now inputs that are not valid import paths (e.g. containing newlines, semicolons, or non-identifier syntax) raise an Error and abort generation instead of being emitted into the generated output. Valid dotted paths (optionally whitespace-padded) continue to work unchanged. (#3763)

additional_imports must be a Python import path composed of identifiers: 'collections.deque\nINJECTION_MARKER = 1'

Default Behavior Changes

• Reserved template keys in --extra-template-data now raise an error for built-in templates - When rendering a built-in (project-owned) template, supplying any generator-reserved key through --extra-template-data (or the extra_template_data API argument) now raises an Error and aborts generation instead of injecting the value. The reserved keys are class_body_lines, config_items, schema_runtime_validation, schema_runtime_validation_base_class_name, schema_runtime_validation_use_base, sequence_base_class, sequence_item_type, sequence_slice_type, _safe_config_items, typed_dict_kwargs, and typed_dict_kwargs_suffix. To inject raw code via these keys you must now use a custom root template through --custom-template-dir. (#3765)
• Stricter extra_template_data validation - extra_template_data that is not a dictionary, contains non-string keys, or contains duplicate (normalized) keys now raises an Error rather than being silently accepted. (#3765)

Code Generation Changes

• Built-in templates now serialize extra_template_data values as non-executing literals - For built-in templates, user-supplied values that were previously emitted as raw Python source are now serialized as quoted, non-executing literals. This affects GraphQL scalar py_type, TypedDict additionalPropertiesType, ConfigDict values, msgspec base_class_kwargs, and comments. Only bare or dotted identifiers (e.g. datetime.date) are still emitted unquoted; more complex expressions become string literals. For example, a scalar py_type supplied as a type expression is now rendered as:

Evil = TypeAliasType("Evil", "__import__('os').system('id') or str")

Trusted custom root templates (--custom-template-dir providing the root template) keep the previous unrestricted raw behavior. (#3765)

• Include-only custom template directories no longer receive raw built-in context - "Custom root" detection changed from template_file_path.is_absolute() to _uses_custom_root_template. A --custom-template-dir that only supplies include/partial templates (not the model's root template) no longer opts the built-in root into the unrestricted raw-context path; its extra_template_data is now treated with the hardened built-in rules (and reserved keys raise an error). (#3765)

... (truncated)

Changelog

Sourced from datamodel-code-generator's changelog.

0.74.0 - 2026-08-17

Breaking Changes

Code Generation Changes

• Non-finite float values now render as structural float(...) expressions - Generated code for non-finite floats (inf, -inf, nan) from Protocol Buffers, XML Schema, and AsyncAPI-embedded schemas — as field defaults, constraint bounds, list items, and enum values — now renders inline as float('inf'), float('-inf'), and float('nan') instead of emitting bare inf/nan literals with an injected from math import inf, nan header. Users relying on the previous output (e.g. snapshot/golden tests, or importing inf/nan from the generated module) will see different generated code (#3770)

# Before
from math import inf
class Model(BaseModel):
value: float | None = inf
After
class Model(BaseModel):
value: float | None = float('inf')

What's Changed

• Update CHANGELOG for 0.73.0 by @​dcg-generated-docs[bot] in koxudaxi/datamodel-code-generator#3767
• Update release benchmark data by @​dcg-generated-docs[bot] in koxudaxi/datamodel-code-generator#3768
• Deploy release benchmark data updates by @​koxudaxi in koxudaxi/datamodel-code-generator#3771
• fix(parser): render non-finite values structurally by @​Aryan-Pardeshi in koxudaxi/datamodel-code-generator#3770

New Contributors

• @​Aryan-Pardeshi made their first contribution in koxudaxi/datamodel-code-generator#3770

Full Changelog: koxudaxi/datamodel-code-generator@0.73.0...0.74.0

---

0.73.0 - 2026-08-15

Breaking Changes

Error Handling Changes

• Additional imports are now validated as Python import paths - Values passed via --additional-imports, the Python config API (GenerateConfig, JSONSchemaParserConfig, etc.), or --extra-template-data must now be dotted sequences of Python identifiers. Previously any value was accepted and split on commas without validation; now inputs that are not valid import paths (e.g. containing newlines, semicolons, or non-identifier syntax) raise an Error and abort generation instead of being emitted into the generated output. Valid dotted paths (optionally whitespace-padded) continue to work unchanged. (#3763)

additional_imports must be a Python import path composed of identifiers: 'collections.deque\nINJECTION_MARKER = 1'

Default Behavior Changes

• Reserved template keys in --extra-template-data now raise an error for built-in templates - When rendering a built-in (project-owned) template, supplying any generator-reserved key through --extra-template-data (or the extra_template_data API argument) now raises an Error and aborts generation instead of injecting the value. The reserved keys are class_body_lines, config_items, schema_runtime_validation, schema_runtime_validation_base_class_name, schema_runtime_validation_use_base, sequence_base_class, sequence_item_type, sequence_slice_type, _safe_config_items, typed_dict_kwargs, and typed_dict_kwargs_suffix. To inject raw code via these keys you must now use a custom root template through --custom-template-dir. (#3765)
• Stricter extra_template_data validation - extra_template_data that is not a dictionary, contains non-string keys, or contains duplicate (normalized) keys now raises an Error rather than being silently accepted. (#3765)

Code Generation Changes

• Built-in templates now serialize extra_template_data values as non-executing literals - For built-in templates, user-supplied values that were previously emitted as raw Python source are now serialized as quoted, non-executing literals. This affects GraphQL scalar py_type, TypedDict additionalPropertiesType, ConfigDict values, msgspec base_class_kwargs, and comments. Only bare or dotted identifiers (e.g. datetime.date) are still emitted unquoted; more complex expressions become string literals. For example, a scalar py_type supplied as a type expression is now rendered as:

</tr></table> 

... (truncated)

Commits

• 5d313d7 fix(parser): render non-finite values structurally (#3770)
• ce97158 Deploy release benchmark data updates (#3771)
• 27f2266 docs: update release benchmark data (#3768)
• 75b132e docs: update CHANGELOG.md for 0.73.0 (#3767)
• f503699 Restrict template source paths (#3766)
• eaacba0 Harden built-in template data (#3765)
• 203bded Merge commit from fork
• 0175464 Validate additional import paths (#3763)
• df05a93 Fix payload runtime validation exclusions (#3764)
• 9ce6a56 Bump the github-actions group with 5 updates (#3751)
• 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)