django.git/tests/contenttypes_tests, branch main

Fixed #36839 -- Warned when model renames encounter conflicts from stale ContentTypes.

2026-02-25T15:22:58Z

Fixed #36935 -- Added fallback in ContentType.app_labeled_name when model_class() is None.

2026-02-21T14:37:46Z

Updated ContentType.app_labeled_name to include the app_label in its string representation. This removed ambiguity for content types whose models were not present in the current codebase (for example, when multiple applications share the same database). Adjusted related tests to reflect the new representation.

Fixed #21961 -- Added support for database-level delete options for ForeignKey.

2025-10-18T13:03:50Z

Thanks Simon Charette for pair programming. Co-authored-by: Nick Stefan Co-authored-by: Akash Kumar Sen <71623442+Akash-Kumar-Sen@users.noreply.github.com> Co-authored-by: Simon Charette

Bumped minimum isort version to 7.0.0.

2025-10-16T18:59:02Z

Added ignores relating to https://github.com/PyCQA/isort/issues/2352.

Refs #28586 -- Split descriptor from GenericForeignKey.

2025-09-18T23:44:16Z

This makes GenericForeignKey more similar to other fields which act as descriptors, preparing it to add “fetcher protocol” support in a clear and consistent way.

Refs #36500 -- Rewrapped long docstrings and block comments via a script.

2025-07-23T23:17:55Z

Rewrapped long docstrings and block comments to 79 characters + newline using script from https://github.com/medmunds/autofix-w505.

Fixed #36267 -- Fixed contenttypes shortcut() view crash with an invalid object_id for a UUIDField pk.

2025-04-02T07:33:13Z

Refs #33651 -- Removed Prefetch.get_current_queryset() and get_prefetch_queryset() per deprecation timeline.

2025-01-15T21:28:37Z

Fixed #35950 -- Restored refreshing of relations when fields deferred.

2024-12-02T15:01:37Z

Thank you to Simon Charette and Sarah Boyce for the review. Regression in 73df8b54a2fab53bec4c7573cda5ad8c869c2fd8.

Fixed #35666 -- Documented stacklevel usage and testing, and adjusted test suite accordingly.

2024-08-28T14:44:05Z

Over the years we've had multiple instances of hit and misses when emitting warnings: either setting the wrong stacklevel or not setting it at all. This work adds assertions for the existing warnings that were declaring the correct stacklevel, but were lacking tests for it.