Special thanks to Hannes Ljungberg for finding multiple implementation
gaps.
Thanks also to Simon Charette and Adam Johnson for reviews.

Special thanks to Hannes Ljungberg for finding multiple implementation
gaps.

Thanks also to Simon Charette, Adam Johnson, and Mariusz Felisiak for
reviews.

…ary conditions.

…nd boundary conditions.

Backport of 352d860 from main.

* upstream/main:
  Refs django#470 -- Fixed field_defaults test failures due to year-end boundary conditions.
  Clarified feature freeze tasks in docs/internals/howto-release-django.txt.
  Fixed #36010 -- Avoided touching mo files while checking writability.
  Fixed #36013 -- Removed use of IDNA-2003 in django.utils.html.
  Refs #27674 -- Removed unused GIS icons.
  Fixed #36125 -- Switched docs to use chat.djangoproject.com when referencing the Discord server.
  Fixed #36114 -- Fixed link visibility when list_display_links field contains only whitespace.
  Switched to pull_request_target event trigger in the Labels Github action.
  Fixed #24529 -- Allowed double squashing of migrations.
  Refs #24529 -- Added replace_migration hook to MigrationLoader.

…-callstring

* upstream/main:
  Refs django#470 -- Fixed field_defaults test failures due to year-end boundary conditions.
  Clarified feature freeze tasks in docs/internals/howto-release-django.txt.
  Fixed #36010 -- Avoided touching mo files while checking writability.
  Fixed #36013 -- Removed use of IDNA-2003 in django.utils.html.
  Refs #27674 -- Removed unused GIS icons.
  Fixed #36125 -- Switched docs to use chat.djangoproject.com when referencing the Discord server.
  Fixed #36114 -- Fixed link visibility when list_display_links field contains only whitespace.
  Switched to pull_request_target event trigger in the Labels Github action.
  Fixed #24529 -- Allowed double squashing of migrations.
  Refs #24529 -- Added replace_migration hook to MigrationLoader.

… boundary conditions.

… boundary conditions.

Determining if a field is db_returning based on the default connection feature
availability prevent the usage of RETURNING for db_default fields in setups
where non-default backends do support RETURNING.

Whether or not the field should be attempted to be returned is already checked
at the compiler level which is backend aware.

Determining if a field is db_returning based on the default connection
feature availability prevents the usage of RETURNING for db_default
fields in setups where non-default backends do support RETURNING.

Whether or not the field should be attempted to be returned is already
checked at the compiler level which is backend aware.

Determining if a field is db_returning based on the default connection
feature availability prevents the usage of RETURNING for db_default
fields in setups where non-default backends do support RETURNING.

Whether or not the field should be attempted to be returned is already
checked at the compiler level which is backend aware.