Prepare for 3.0.0 release

CHANGELOG.md

@@ -1,14 +1,18 @@
 # Django CTE change log
 
-## 3.0.0 - unreleased
+## 3.0.0 - 2026-02-05
 
 - **BREAKING:** on Django 5.2 and later when joining a CTE to a queryset with
   LEFT OUTER JOIN (`_join_type=LOUTER`) and the join condition implicitly joins
   a related table, the implicit join is now a LEFT OUTER JOIN instead of an
   INNER JOIN. This makes the join behavior match SQL database semantics: the
   left-side rows are always preserved. To restore the old behavior, either
   do not use `_join_type=LOUTER` or add extra WHERE conditions as needed.
-  See https://github.com/dimagi/django-cte/pull/130 for more details.
+  See [#130](https://github.com/dimagi/django-cte/pull/130) for more details.
+- Fixed `CTE.queryset()` queries involving aggregates ([#128](https://github.com/dimagi/django-cte/issues/128)).
+- Fixed Django 5.2 ambiguous column names bug ([#127](https://github.com/dimagi/django-cte/issues/127)).
+- Fixed possible ambiguous column names in SQL ([#125](https://github.com/dimagi/django-cte/issues/125)).
+- Fixed Django 5.2 `CTE.queryset()` regression ([#124](https://github.com/dimagi/django-cte/pull/124)).
 
 ## 2.0.0 - 2025-06-16
 

django_cte/__init__.py

@@ -1,4 +1,4 @@
 from .cte import CTE, with_cte, CTEManager, CTEQuerySet, With  # noqa
 
-__version__ = "2.0.1"
+__version__ = "3.0.0"
 __all__ = ["CTE", "with_cte"]