chore: release 0.14.0

[FabianClemenz]

Summary

Release 0.14.0 — a minor bump for the new --base-classes option, plus the comparison-page correction.

Nothing but release mechanics: [Unreleased] → [0.14.0] with the compare-link footer, version bump, uv lock, and the documented pre-commit rev: moved to v0.14.0 in both docs/usage/ci.md and the example inside .pre-commit-hooks.yaml.

What ships

Added — --base-classes (#173, partially addresses #171). Names extra base classes to treat as Pydantic models, for bases defined outside the scanned files. Unblocks django-ninja Schema subclasses, and the shared BaseSchema from an internal library.

Fixed — the comparison page (#172). Two rows claimed no alternative ships Markdown injection or a CI drift gate; paracelsus ships both. It is now a column and a named entry under "when to use something else".

Non-breaking in both directions: a new optional flag and a docs correction. Anyone on 0.13.0 can upgrade without changing anything.

Why now rather than bundled later

--base-classes is the django-ninja angle, and that is only claimable in a launch post if pip install erdify actually delivers it. The docs site already redeployed from main, so until this ships the site and PyPI disagree about what erdify can do.

Type of change

• Refactor / maintenance

Verification

uv run pytest                 341 passed
uv run ruff check / mypy      clean
uv run erdify --version       erdify 0.14.0
mkdocs build --strict         passes

uv.lock re-synced in the same commit — the erdify entry is pinned and goes stale otherwise, which the uv-lock pre-commit hook confirms.

After merge

Same flow as 0.13.0: I tag v0.14.0, publish the GitHub release and post the announcement Discussion. The PyPI publish then sits in the gated pypi environment waiting for your Review deployments → Approve — that click stays yours.

One note for the launch copy

--base-classes handles ninja.Schema subclasses with explicit field annotations. It does not handle ninja.ModelSchema, whose fields come from an inner Meta. Any post claiming "django-ninja support" should say which half, or the first Ninja user reaching for ModelSchema writes the top comment. #171 stays open for that.

Checklist

• Tests added or updated for the change — n/a, release mechanics
• uv run pytest passes locally
• uv run ruff check src/ tests/ and uv run mypy src/ pass
• Docs/README updated if behavior changed
• CHANGELOG.md updated under [Unreleased]

[datadog-devsuit]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 93.29% (+0.00%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 1c2f6d1 | Docs | View more details | Give us feedback!}