Skip to content

Update datamodel-code-generator requirement from <0.66,>=0.61 to >=0.61,<0.72 - #618

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/datamodel-code-generator-gte-0.61-and-lt-0.72
Open

Update datamodel-code-generator requirement from <0.66,>=0.61 to >=0.61,<0.72#618
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/datamodel-code-generator-gte-0.61-and-lt-0.72

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 27, 2026

Copy link
Copy Markdown
Contributor

Updates the requirements on datamodel-code-generator to permit the latest version.

Release notes

Sourced from datamodel-code-generator's releases.

0.71.0

Breaking Changes

Default Behavior Changes

  • New warning emitted by default for unresolved local $ref pointers - By default, an unresolved local $ref JSON pointer now emits a new DanglingRefWarning and generates a fallback Any model. Previously such refs resolved to a silent fallback, and some cases (e.g., out-of-range JSON pointer array indices) raised a hard error. Schemas that previously generated cleanly can now produce warnings, which breaks workflows that treat warnings as errors (e.g., python -W error). Use --strict-refs to fail on unresolved pointers instead, or --disable-warnings to silence them (#3639)

Error Handling Changes

  • $ref to a non-dict file now raises InvalidFileFormatError instead of TypeError - Resolving a $ref to a JSON/YAML file whose top-level value is not a mapping (e.g., a list) now raises datamodel_code_generator.InvalidFileFormatError (a subclass of Error/Exception) rather than the built-in TypeError. Programmatic callers that catch TypeError around generate() must catch InvalidFileFormatError (or Error) instead (#3639)
  • Malformed-input diagnostics reworded - Malformed inputs that previously surfaced an uncaught traceback now emit a concise message such as Invalid file format for <type> at <source>: ..., and the missing-file message changed from File not found to File not found: <path>. Tooling that matches on the exact previous strings needs updating (#3639)
  • Generation now aborts when output paths would overwrite inputs or collide - A new path-conflict validation runs before generation in both the generate() Python API and the CLI. Invocations that previously succeeded now raise an Error (CLI exits with an error code) in these cases: the output path resolves to an existing input file, the --emit-model-metadata path resolves to an existing input file, or the output and model-metadata paths resolve to the same file. Symlinks and hardlinks are resolved before the comparison. Workflows that intentionally wrote output over an input path, or that pointed the model-metadata artifact at the same path as the output, will now fail with one of:
Output path must not overwrite an input path: <path>
Model metadata path must not overwrite an input path: <path>
Output and model metadata paths must be different: <path>

(#3647)

What's Changed

... (truncated)

Changelog

Sourced from datamodel-code-generator's changelog.

0.71.0 - 2026-07-24

Breaking Changes

Default Behavior Changes

  • New warning emitted by default for unresolved local $ref pointers - By default, an unresolved local $ref JSON pointer now emits a new DanglingRefWarning and generates a fallback Any model. Previously such refs resolved to a silent fallback, and some cases (e.g., out-of-range JSON pointer array indices) raised a hard error. Schemas that previously generated cleanly can now produce warnings, which breaks workflows that treat warnings as errors (e.g., python -W error). Use --strict-refs to fail on unresolved pointers instead, or --disable-warnings to silence them (#3639)

Error Handling Changes

  • $ref to a non-dict file now raises InvalidFileFormatError instead of TypeError - Resolving a $ref to a JSON/YAML file whose top-level value is not a mapping (e.g., a list) now raises datamodel_code_generator.InvalidFileFormatError (a subclass of Error/Exception) rather than the built-in TypeError. Programmatic callers that catch TypeError around generate() must catch InvalidFileFormatError (or Error) instead (#3639)
  • Malformed-input diagnostics reworded - Malformed inputs that previously surfaced an uncaught traceback now emit a concise message such as Invalid file format for <type> at <source>: ..., and the missing-file message changed from File not found to File not found: <path>. Tooling that matches on the exact previous strings needs updating (#3639)
  • Generation now aborts when output paths would overwrite inputs or collide - A new path-conflict validation runs before generation in both the generate() Python API and the CLI. Invocations that previously succeeded now raise an Error (CLI exits with an error code) in these cases: the output path resolves to an existing input file, the --emit-model-metadata path resolves to an existing input file, or the output and model-metadata paths resolve to the same file. Symlinks and hardlinks are resolved before the comparison. Workflows that intentionally wrote output over an input path, or that pointed the model-metadata artifact at the same path as the output, will now fail with one of:
Output path must not overwrite an input path: <path>
Model metadata path must not overwrite an input path: <path>
Output and model metadata paths must be different: <path>

(#3647)

What's Changed

... (truncated)

Commits

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
Update datamodel-code-generator requirement
87ac314 
Updates the requirements on [datamodel-code-generator](https://github.com/koxudaxi/datamodel-code-generator) to permit the latest version.
- [Release notes](https://github.com/koxudaxi/datamodel-code-generator/releases)
- [Changelog](https://github.com/koxudaxi/datamodel-code-generator/blob/main/CHANGELOG.md)
- [Commits](koxudaxi/datamodel-code-generator@0.61.0...0.71.0)

---
updated-dependencies:
- dependency-name: datamodel-code-generator
  dependency-version: 0.71.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Jul 27, 2026
@dependabot dependabot Bot mentioned this pull request Jul 27, 2026
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants