Skip to content

fix(neo4j): dump the entrypoint report through the pydantic compat shim - #188

Merged
rahlk merged 1 commit into
mainfrom
fix/neo4j-report-pydantic-v1
Sep 6, 2026
Merged

fix(neo4j): dump the entrypoint report through the pydantic compat shim#188
rahlk merged 1 commit into
mainfrom
fix/neo4j-report-pydantic-v1

Conversation

@rahlk

@rahlk rahlk commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

The v1.4.1 release run failed its Python 3.10 compat leg: :PyApplication.entrypoint_report_json called model_dump(), a pydantic v2 method, and that leg resolves pydantic 1.x, so every --emit neo4j run raised. Routed through codeanalyzer.schema.model_dump (.dict()/.json() on v1). Verified under pydantic 1.10.26 and 2.x; the tag is re-cut on this commit.

`:PyApplication.entrypoint_report_json` called `model_dump()` on the report,
a pydantic v2 method. The Python 3.10 leg of the release gate resolves
pydantic 1.x, where every `--emit neo4j` run raised. Route it through
`codeanalyzer.schema.model_dump`, which maps to `.dict()`/`.json()` on v1.
Verified under pydantic 1.10.26 and 2.x.
@rahlk
rahlk merged commit 46e398c into main Sep 6, 2026
@rahlk
rahlk deleted the fix/neo4j-report-pydantic-v1 branch September 6, 2026 00:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant