Closed
Description
This is a patch release dealing with a number of unforeseen issues in 3.15.0.
Please see #9270 for discussion on the project management, and ensuring we're able to get into a much more carefully considered release process for future releases.
(In brief: The project should broadly just be tracking Django versions, and dealing with required security fixes. We need a much higher bar to accepting contributions, and need some clear guidelines to help us manage that process with as little noise and churn as possible.)
The following change has been fixed...
The following changes have all been reverted, for the time being...
- 3.15 regression: UpdateModelMixin breaks views using Manager objects as queryset #9319 - Resolved via Revert "Re-prefetch related objects after updating" #9327
- 3.15 regression: ListSerializer ValidationErrors silently changed return type #9317 - Resolved via Revert "feat: Add some changes to ValidationError to support django style vad…" #9326
- New handling of default= for ModelSerializer #9310 - Resolved via Revert #9030 #9333
- 3.15 not backwards compatible with 3.14 - "View' should either include a
querysetattribute, or override theget_queryset()method." #9306 - Resolved via Revert "Re-prefetch related objects after updating" #9327 -
permissions.DjangoModelPermissionsOrAnonReadOnlydoesn't actually enable anonymous read-only access in 3.15 #9299 - Resolved via Revert #8009 #9332 - 3.15.0 - bug in rendering
%characters fromValidationError#9295 - Resolved via Revert #8863 #9330 - Error: An admin for model "User" has to be registered to be referenced by TokenAdmin.autocomplete_fields. #9300 - Resolved via TokenAdmin.autocomplete_fields Breaks Some Use Cases, Revert #9301
- 3.15 regression: Unset default namespace version suddenly raises 404 #9334 - Resolved via Revert "Fix NamespaceVersioning ignoring DEFAULT_VERSION on non-None namespaces" #9335
Metadata
Metadata
Assignees
Labels
No labels