v0.26.25 (2026-08-08)
Documentation
- docs: point users to castiron, the successor (#142)
supabase-pydantic's README and docs contained zero mentions of castiron, so
its users had no way to learn the successor exists. This adds the pointer and
states the project's status plainly.
- README: a maintenance-mode notice under the intro — fixes and dependency
updates continue, nothing is being removed, and no end-of-life date has been
set; new feature work has moved to castiron. - New docs page (getting-started/castiron.md) with a shipped-vs-not capability
table, the OpenAPI source's blind spots, and an explicit "there is no
automated migration" section. - Welcome page: a status admonition linking that page.
- mkdocs nav: one entry for the new page.
Deliberately conservative about castiron: it is 0.1.0 and pre-alpha, with one
command, one source (OpenAPI/PostgREST) and one emitter (Pydantic v2). It does
not connect to a live database, emit SQLAlchemy models, read MySQL, or generate
seed data — all of which supabase-pydantic does today. The "should you move
yet?" section leads with "stay". No EOL or deprecation date is announced,
because none has been decided.
Also drops two forward-looking clauses ("more updates are coming!",
"more models & database support to come") that the new notice contradicts.
Prose only: no code, no CHANGELOG.md, no version change. @kmbhm1 (74d5bf8)
