[v0.5.53] — ORM Query Semantics & Migration Generation Correctness

[nagarjuna-tella]

v0.5.53 fixes two correctness areas that share the same root problem: code that appeared to work but produced subtly wrong output.

NULL filtering that returned no rows instead of null rows. FK filters that rejected valid column aliases. Migration generation that emitted tables in the wrong order. These aren't crashes — they're the kind of wrong behavior that causes you to doubt your data before you doubt the framework.

This release fixes them.

---

Foundation hardening sequence

Version	Area
v0.5.50	Migration safety
v0.5.51	ORM primitive field correctness
v0.5.52	Admin correctness & permissions
v0.5.53	ORM query semantics & migration generation

---

Validation

• Full suite: 7709 passed, 3 skipped
• Migrations suite: 514 passed
• Security suite: 729 passed, 1 skipped
• Tasks suite: 23 passed
• MkDocs strict build: passing
• pip-audit: passing, no known vulnerabilities

---

Install

pip install aksara-framework==0.5.53

---

What's Next

The remaining ORM correctness work:

• Write-path consistency — bulk_create, upsert, QuerySet.update() aligned with save() semantics
• QuerySet.update() and updated_at
• Vector bulk_update() casting
• Relation DDL safety
• Array, vector, file, and image advanced field policy

---

Aksara is pre-1.0 and does not claim production readiness.

---

This discussion was created from the release [v0.5.53] — ORM Query Semantics & Migration Generation Correctness.