Repository: typeddjango/django-stubs

Issue:
Next release planning (4.2.5)
__TODO:__
- [x] #1719 
- [x] Add plugin support for `users = ManyToManyField(settings.AUTH_USER_MODEL)` #1746 

#1719 introduces plugin support for `ManyToManyField` but is lacking support for passing `AUTH_USER_MODEL` as `to=` arg e.g.:

```python
users = ManyToManyField(settings.AUTH_USER_MODEL)
```

Which we suspect is a normal use case and should support in any next release.

---

Please comment on this issue if there's anything else you know should, or want to be included.


Discussion:
And for anyone feeling adventurous, please try out `HEAD` on your project(s) and report back here if you run in to anything you think is a new issue. Perhaps we can then resolve it before pushing out a release.
Now that mypy 1.6.0 is out, we should consider making a release with the `compatible-mypy` bump. I can do the release.

I'd consider this a blocker, since it's a regression and we already have a fix PR:

* https://github.com/typeddjango/django-stubs/pull/1745

I'm releasing djangorestframework-stubs too, any takers to review this for the release:
* https://github.com/typeddjango/djangorestframework-stubs/pull/482

It'd be nice if we could also include #1767 in the next release
I want to move forward with:

* https://github.com/typeddjango/django-stubs/issues/1628

Making no changes quite yet, but I propose mentioning in 4.2.5 release notes that the next next version (4.2.6) will remove hard mypy dependency. Something like:

<details>

<summary>(outdated text)</summary>

> django-stubs is taking steps to improve experience with other type checkers besides mypy. Next version (4.2.6) will remove explicit mypy dependency. If you are currently using mypy, please add an explicit dev dependency on `mypy` to your project, or depend on django-stubs with the `compatble-mypy` extra, e.g. `django-stubs[compatible-mypy]`.
> **Note:** this is not a guarantee that other type checkers will be fully supported, pull requests for improvements are welcome. See [#1628](https://github.com/typeddjango/django-stubs/issues/1628) for details.

</details>

If you have comments on this, please discuss in #1628.

Should I cut the release or wait for the `cached_property` work to be completed?

* #1771
* #1761
* #1768
* #1769

We could always push another release if we want to. If you feel that one is due
I think `property` stuff can wait, really.

Resolving patch:
diff --git a/ext/setup.py b/ext/setup.py
--- a/ext/setup.py
+++ b/ext/setup.py
@@ -15,7 +15,7 @@
 # It's fine to skip django-stubs-ext releases, but when doing a release, update this to newest django-stubs version.
 setup(
     name="django-stubs-ext",
-    version="4.2.2",
+    version="4.2.5",
     description="Monkey-patching and extensions for django-stubs",
     long_description=readme,
     long_description_content_type="text/markdown",
diff --git a/setup.py b/setup.py
--- a/setup.py
+++ b/setup.py
@@ -23,7 +23,7 @@ def find_stub_files(name: str) -> List[str]:
 dependencies = [
     "mypy>=1.0.0",
     "django",
-    "django-stubs-ext>=4.2.2",
+    "django-stubs-ext>=4.2.5",
     "tomli; python_version < '3.11'",
     # Types:
     "typing-extensions",
@@ -38,7 +38,7 @@ def find_stub_files(name: str) -> List[str]:
 
 setup(
     name="django-stubs",
-    version="4.2.4",
+    version="4.2.5",
     description="Mypy stubs for Django",
     long_description=readme,
     long_description_content_type="text/markdown",


Test patch: