Django ORM fix week and calendar versioning prep

What shipped: Django fixed several ORM regressions this week, including a changelist search crash and over-matching in __exact [1], a QuerySet.distinct() crash on duplicated selections [2], annotation preservation and key selection in in_bulk() [3], and prevention of consumption of rhs iterators in annotation lookups [4]. The core also corrected equality and XML serialization for unsaved composite primary keys [5] and improved RelatedIn lookup preparation performance [11]. On the djangoproject.com front, search performance improved [7], with a deterministic sort and reduced headline calculations [8][9].

Why it matters: These fixes address crashes and over-matching that could affect changelist searches and ORM queries in your applications. The composite primary key support is relatively new, so if you use it, the equality and serialization corrections matter for data integrity [5]. The search performance work on djangoproject.com doesn't directly affect your code, but the deterministic sort sets a better example for search result consistency [8].

What's next: Django is preparing for calendar versioning. Deprecation warnings now use calendar-based names [10], and version tuples support the new scheme [11]. Expect these changes to surface in future releases, so review your code for deprecation warnings that will shift naming conventions.

Also: djangoproject.com fixed docs search fragments [1], restored the Benevity link, updated the Teams page heading [12], removed a duplicate "Back to top" link [13], and added community package mentions to the docs [14].