[v0.5.54] — ORM Write & Relation Correctness #14
nagarjuna-tella
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
v0.5.54 addresses the cross-path inconsistency identified in the ORM correctness audit:
bulk_create,QuerySet.update, and relation configuration producing different behavior than equivalentsave()calls for the same data.The rule this release enforces: if
save()does it, every write path should do it. Same validation, same field preparation, same auto-field behavior. No surprises depending on which write path you used.Foundation hardening sequence
Validation
pip-audit: passing, no known vulnerabilitiesInstall
What's Next
The remaining ORM correctness work:
FileField/ImageField.to_python()contractAksara is pre-1.0 and does not claim production readiness.
This discussion was created from the release [v0.5.54] — ORM Write & Relation Correctness.
All reactions