koxudaxi/datamodel-code-generator - CodSpeed

datamodel-code-generator

Blog Docs Changelog

Performance History

Latest Results

Rename input fixture to match expected output filename Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

butvinm:fix/type-statement-empty-fields-crash

10 hours ago

Skip reuse_model type alias test on old black versions Black 22/23 can't parse Python 3.14 type statement syntax. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

butvinm:fix/type-statement-empty-fields-crash

12 hours ago

Fix same empty fields crash in UnionTypeAliasAnnotation and UnionTypeAliasType These two union templates had the identical unguarded fields[0] access. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

butvinm:fix/type-statement-empty-fields-crash

12 hours ago

Fix type alias template crash when reuse_model creates empty fields Guard fields[0] access in TypeStatement, TypeAliasType, TypeAliasAnnotation, and UnionTypeStatement templates. When fields is empty (reuse model), fall back to base_class, producing e.g. `type Foo = Bar`. Fixes #3059 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

butvinm:fix/type-statement-empty-fields-crash

12 hours ago

Add --no-allow-remote-refs to CLI_OPTION_META BooleanOptionalAction registers both --allow-remote-refs and --no-allow-remote-refs in argparse; the sync test requires both to be in CLI_OPTION_META. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

butvinm:fix/allow-remote-refs

2 days ago

Support --no-allow-remote-refs via BooleanOptionalAction Use BooleanOptionalAction (like --use-annotated) so users can explicitly opt out with --no-allow-remote-refs from the CLI. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

butvinm:fix/allow-remote-refs

2 days ago

Change --allow-remote-refs default to warn instead of block Per maintainer feedback, keep backward compatibility by allowing remote $ref fetching by default but emit a FutureWarning when it happens without explicit --allow-remote-refs. The flag becomes a three-state: True (explicit opt-in, no warning), False (blocks), None (default, allows with deprecation warning). The default will flip to False in a future major version. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

butvinm:fix/allow-remote-refs

4 days ago

Update release draft model and preserve breaking changes (#3057)

main

4 days ago

Latest Branches

-2%

Fix type alias template crash with reuse_model on empty fields#3060

10 hours ago

1ad2e58

butvinm:fix/type-statement-empty-fields-crash

-3%

Add --allow-remote-refs to disable HTTP fetching of $ref by default#3051

2 days ago

031ca0e

butvinm:fix/allow-remote-refs

+3%

Update release draft model and preserve breaking changes#3057

4 days ago

60e3376

release-draft-opus-46

© 2026 CodSpeed Technology

Home Terms Privacy Docs