Build: Bump datamodel-code-generator from 0.41.0 to 0.52.1

[dependabot]

Bumps datamodel-code-generator from 0.41.0 to 0.52.1.

Release notes

Sourced from datamodel-code-generator's releases.

0.52.1

What's Changed

• Add --validators option for Pydantic v2 field validators by @​koxudaxi in koxudaxi/datamodel-code-generator#2906
• Add dynamic model generation support by @​koxudaxi in koxudaxi/datamodel-code-generator#2901
• Sync zensical.toml nav with docs directory by @​koxudaxi in koxudaxi/datamodel-code-generator#2908
• Add deprecation warning for default output-model-type by @​koxudaxi in koxudaxi/datamodel-code-generator#2910
• Add deprecation warning and explicit --output-model-type to docs by @​koxudaxi in koxudaxi/datamodel-code-generator#2911
• Add llms.txt generator for LLM-friendly documentation by @​koxudaxi in koxudaxi/datamodel-code-generator#2912
• Move coverage fail_under check to combined coverage environment by @​koxudaxi in koxudaxi/datamodel-code-generator#2909
• Fix YAML scientific notation parsing as float by @​koxudaxi in koxudaxi/datamodel-code-generator#2913
• Add deprecated field support for Pydantic v2 by @​koxudaxi in koxudaxi/datamodel-code-generator#2915
• Add deprecation warning for Pydantic v2 without --use-annotated by @​koxudaxi in koxudaxi/datamodel-code-generator#2914

Full Changelog: koxudaxi/datamodel-code-generator@0.52.0...0.52.1

0.52.0

Breaking Changes

Code Generation Changes

• Union fields with titles now wrapped in named models when --use-title-as-name is enabled - Previously, union-typed fields with a title were generated as inline union types (e.g., TypeA | TypeB | TypeC | None). Now they generate a separate wrapper model using the title name, and the field references this wrapper type (e.g., ProcessingStatusUnionTitle | None). This affects code that directly accesses union field values, as they now need to access the .root attribute (Pydantic v2) or .__root__ (Pydantic v1) of the wrapper model. (#2889) Before:

  class ProcessingTaskTitle(BaseModel):
      processing_status_union: (
          ProcessingStatusDetail | ExtendedProcessingTask | ProcessingStatusTitle | None
      ) = Field('COMPLETED', title='Processing Status Union Title')

  After:

  class ProcessingStatusUnionTitle(BaseModel):
      __root__: (
          ProcessingStatusDetail | ExtendedProcessingTask | ProcessingStatusTitle
      ) = Field(..., title='Processing Status Union Title')
  class ProcessingTaskTitle(BaseModel):
      processing_status_union: ProcessingStatusUnionTitle | None = Field(
          default_factory=lambda: ProcessingStatusUnionTitle.parse_obj('COMPLETED'),
          title='Processing Status Union Title',
      )

• Inline types with titles now generate named type aliases when --use-title-as-name is enabled - Arrays, dicts, enums-as-literals, and oneOf/anyOf unions that have a title in the schema now generate named type aliases or RootModel classes instead of being inlined. This improves readability but changes the generated type structure. For TypedDict output, generates type MyArrayName = list[str]. For Pydantic output, generates class MyArrayName(RootModel[list[str]]). (#2889)
• Default value handling changed for wrapped union fields - Fields that previously had simple default values now use default_factory with a lambda that calls parse_obj() (Pydantic v1) or model_validate() (Pydantic v2) to construct the wrapper model. Code that introspects field defaults will see a factory function instead of a direct value. (#2889)
• Different output for $ref with nullable: true - When a JSON Schema property has a $ref combined with only nullable: true (and optionally metadata like title/description), the generator now uses the referenced type directly with Optional annotation instead of creating a new merged model. For example, a schema with multiple properties referencing User with nullable: true will now generate user_a: User | None instead of creating separate UserA, UserB model classes. This is a bug fix that reduces redundant model generation, but existing code that depends on the previously generated class names will break. (#2890) Before:

  class UserA(BaseModel):
      name: str

... (truncated)

Changelog

Sourced from datamodel-code-generator's changelog.

0.52.1 - 2026-01-03

What's Changed

• Add --validators option for Pydantic v2 field validators by @​koxudaxi in koxudaxi/datamodel-code-generator#2906
• Add dynamic model generation support by @​koxudaxi in koxudaxi/datamodel-code-generator#2901
• Sync zensical.toml nav with docs directory by @​koxudaxi in koxudaxi/datamodel-code-generator#2908
• Add deprecation warning for default output-model-type by @​koxudaxi in koxudaxi/datamodel-code-generator#2910
• Add deprecation warning and explicit --output-model-type to docs by @​koxudaxi in koxudaxi/datamodel-code-generator#2911
• Add llms.txt generator for LLM-friendly documentation by @​koxudaxi in koxudaxi/datamodel-code-generator#2912
• Move coverage fail_under check to combined coverage environment by @​koxudaxi in koxudaxi/datamodel-code-generator#2909
• Fix YAML scientific notation parsing as float by @​koxudaxi in koxudaxi/datamodel-code-generator#2913
• Add deprecated field support for Pydantic v2 by @​koxudaxi in koxudaxi/datamodel-code-generator#2915
• Add deprecation warning for Pydantic v2 without --use-annotated by @​koxudaxi in koxudaxi/datamodel-code-generator#2914

Full Changelog: koxudaxi/datamodel-code-generator@0.52.0...0.52.1

---

0.52.0 - 2026-01-02

Breaking Changes

Code Generation Changes

• Union fields with titles now wrapped in named models when --use-title-as-name is enabled - Previously, union-typed fields with a title were generated as inline union types (e.g., TypeA | TypeB | TypeC | None). Now they generate a separate wrapper model using the title name, and the field references this wrapper type (e.g., ProcessingStatusUnionTitle | None). This affects code that directly accesses union field values, as they now need to access the .root attribute (Pydantic v2) or .__root__ (Pydantic v1) of the wrapper model. (#2889) Before:

  class ProcessingTaskTitle(BaseModel):
      processing_status_union: (
          ProcessingStatusDetail | ExtendedProcessingTask | ProcessingStatusTitle | None
      ) = Field('COMPLETED', title='Processing Status Union Title')

  After:

  class ProcessingStatusUnionTitle(BaseModel):
      __root__: (
          ProcessingStatusDetail | ExtendedProcessingTask | ProcessingStatusTitle
      ) = Field(..., title='Processing Status Union Title')
  class ProcessingTaskTitle(BaseModel):
      processing_status_union: ProcessingStatusUnionTitle | None = Field(
          default_factory=lambda: ProcessingStatusUnionTitle.parse_obj('COMPLETED'),
          title='Processing Status Union Title',
      )

• Inline types with titles now generate named type aliases when --use-title-as-name is enabled - Arrays, dicts, enums-as-literals, and oneOf/anyOf unions that have a title in the schema now generate named type aliases or RootModel classes instead of being inlined. This improves readability but changes the generated type structure. For TypedDict output, generates type MyArrayName = list[str]. For Pydantic output, generates class MyArrayName(RootModel[list[str]]). (#2889)
• Default value handling changed for wrapped union fields - Fields that previously had simple default values now use default_factory with a lambda that calls parse_obj() (Pydantic v1) or model_validate() (Pydantic v2) to construct the wrapper model. Code that introspects field defaults will see a factory function instead of a direct value. (#2889)
• Different output for $ref with nullable: true - When a JSON Schema property has a $ref combined with only nullable: true (and optionally metadata like title/description), the generator now uses the referenced type directly with Optional annotation instead of creating a new merged model. For example, a schema with multiple properties referencing User with nullable: true will now generate user_a: User | None instead of creating separate UserA, UserB model classes. This is a bug fix that reduces redundant model generation, but existing code that depends on the previously generated class names will break. (#2890)

... (truncated)

Commits

• 361fb5a Add deprecation warning for Pydantic v2 without --use-annotated (#2914)
• 69c51fd Add deprecated field support for Pydantic v2 (#2915)
• b5a361d Fix YAML scientific notation parsing as float (#2913)
• c1682ac Move coverage fail_under check to combined coverage environment (#2909)
• c83470e Add llms.txt generator for LLM-friendly documentation (#2912)
• e12cd96 Add deprecation warning and explicit --output-model-type to docs (#2911)
• f2859a6 Add deprecation warning for default output-model-type (#2910)
• dcc5567 Sync zensical.toml nav with docs directory (#2908)
• 44934ce Add dynamic model generation support (#2901)
• a2b2756 Add --validators option for Pydantic v2 field validators (#2906)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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 #403.