fix(deps): update dependency strawberry-graphql-django to v0.89.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
strawberry-graphql-django	==0.47.1 → ==0.89.2

---

Release Notes

strawberry-graphql/strawberry-django (strawberry-graphql-django)

v0.89.2

Compare Source

Fix nullable connections (e.g. when guarded by a permission extension) eagerly
fetching the entire table before the connection applied its pagination. The
return type is now unwrapped from StrawberryOptional/other containers so the
queryset evaluation stays deferred and the connection can apply a LIMIT.

This release was contributed by @​rcybulski1122012 in #​953

v0.89.1

Compare Source

Permission extensions are now fully compatible with strawberry-graphql >= 0.326.0, which enforces strict type uniqueness for custom schema directives during schema construction.

Previously, DjangoPermissionExtension.schema_directive created a new anonymous AutoDirective class on every extension instantiation without caching it on the underlying class.
When the same permission extension (e.g. IsSuperuser(), IsAuthenticated(), or custom subclasses) was attached to multiple fields, Strawberry raised a ValueError reporting duplicate directive definitions for the same directive name.

The generated AutoDirective class is now cached on self.__class__ via __dict__.get():

@functools.cached_property
def schema_directive(self) -> object:
    key = "__strawberry_directive_type__"
    directive_class = self.__class__.__dict__.get(key)

    if directive_class is None:

        @schema_directive(
            name=self.__class__.__name__,
            locations=self.SCHEMA_DIRECTIVE_LOCATIONS,
            description=self.SCHEMA_DIRECTIVE_DESCRIPTION,
            repeatable=True,
        )
        class AutoDirective: ...

        directive_class = AutoDirective
        setattr(self.__class__, key, directive_class)

    return directive_class()

This ensures a single, reusable schema directive type is created per extension class, eliminating duplicate directive collisions while preserving full isolation across subclasses and maintaining backward compatibility with older Strawberry versions.

This release was contributed by @​daudln in #​951

Additional contributors: @​bellini666, @​Copilot, @​pre-commit-ci[bot]

v0.89.0

Compare Source

Require Strawberry GraphQL 0.322.2 or newer, which fixes Relay pagination when combining first with before. Update compatibility tests for the corrected pagination behavior and make schema comparisons independent of top-level definition order.

Update GraphQL-core 3.3 compatibility for the 3.3.0rc0 execution API, preserving resolve-info context and adapting fragment and variable values used by the query optimizer.

This release was contributed by @​patrick91 in #​955

Additional contributors: @​pre-commit-ci[bot]

v0.88.1

Compare Source

Permission extensions are now fully compatible with strawberry-graphql >= 0.326.0, which enforces strict type uniqueness for custom schema directives during schema construction.

Previously, DjangoPermissionExtension.schema_directive created a new anonymous AutoDirective class on every extension instantiation without caching it on the underlying class.
When the same permission extension (e.g. IsSuperuser(), IsAuthenticated(), or custom subclasses) was attached to multiple fields, Strawberry raised a ValueError reporting duplicate directive definitions for the same directive name.

The generated AutoDirective class is now cached on self.__class__ via __dict__.get():

@functools.cached_property
def schema_directive(self) -> object:
    key = "__strawberry_directive_type__"
    directive_class = self.__class__.__dict__.get(key)

    if directive_class is None:

        @schema_directive(
            name=self.__class__.__name__,
            locations=self.SCHEMA_DIRECTIVE_LOCATIONS,
            description=self.SCHEMA_DIRECTIVE_DESCRIPTION,
            repeatable=True,
        )
        class AutoDirective: ...

        directive_class = AutoDirective
        setattr(self.__class__, key, directive_class)

    return directive_class()

This ensures a single, reusable schema directive type is created per extension class, eliminating duplicate directive collisions while preserving full isolation across subclasses and maintaining backward compatibility with older Strawberry versions.

This release was contributed by @​daudln in #​949

Additional contributors: @​Copilot, @​bellini666, @​pre-commit-ci[bot]

v0.88.0

Compare Source

Allow mutations with Django error handling to return interfaces by expanding them to their concrete implementations.

This release was contributed by @​Guflly in #​939

Additional contributors: @​bellini666

v0.87.1

Compare Source

Fix the query optimizer dropping a manually applied select_related from the
only() mask when another field on the same model shares its name as a
prefix without a __ boundary (e.g. company vs company_branch). This
previously made Django raise FieldError: cannot be both deferred and traversed using select_related at the same time whenever only the longer
sibling was selected in the query.

This release was contributed by @​cjcontreras in #​945

v0.87.0

Compare Source

Resolve prefetch-optimized nested connections on the event loop instead of
paying a sync_to_async thread hop per parent node: the nested-connection
default resolver, the queryset hook for prefetch-optimized querysets and
totalCount served from the prefetched window annotation no longer touch
the database, so they no longer need a worker thread.

This release was contributed by @​rcybulski1122012 in #​932

Additional contributors: @​Copilot

v0.86.8

Compare Source

The built-in toolbar script is now compatible with django-debug-toolbar 7.0.0,
which renders the toolbar inside a shadow DOM by default.

Previously, all DOM queries targeted #djDebug directly on the document,
which broke under shadow DOM isolation — querySelector cannot pierce a shadow
boundary.

Using a getDebugElement() helper that locates #djDebug via
the shadow root of its parent element (#djDebugRoot):

function getDebugElement() {
  const root = document.getElementById("djDebugRoot");
  if (root) {
    return (root.shadowRoot || root).querySelector("#djDebug");
  }
  return document.getElementById("djDebug");
}

This also handles the USE_SHADOW_DOM = False fallback gracefully, keeping
backward compatibility with older versions of the toolbar.

This release was contributed by @​daudln in #​926

Additional contributors: @​bellini666, @​pre-commit-ci[bot], @​Copilot

v0.86.7

Compare Source

Honor the DEFAULT_PK_FIELD_NAME setting (and per-field key_attr) when
resolving existing instances in mutation inputs. Previously _parse_pk read the
input value under key_attr but always looked the instance up by pk=, so
relation inputs and bare-id updates that reference an object by a configured
non-pk field raised DoesNotExist or matched the wrong row. Filters already
honored the setting; mutations now do too. The default pk-based path is
unchanged.

This release was contributed by @​ayushin in #​928

v0.86.6

Compare Source

Fix an N+1 on totalCount of nested connections optimized by prefetching:
parents whose prefetched first-page partition came back empty issued one
COUNT(*) query each, even though an empty first page already proves the
total count is 0.

This release was contributed by @​rcybulski1122012 in #​931

Additional contributors: @​Copilot

v0.86.5

Compare Source

Document the Django validation cache extension and its Django cache backend options.

This release was contributed by @​w3lld1 in #​934

v0.86.4

Compare Source

@strawberry_django.type types no longer overwrite is_type_of methods in superclasses.
Instead, the superclass' result will be taken into account as well.

This release was contributed by @​diesieben07 in #​922

v0.86.3

Compare Source

Connection resolvers can now be annotated with a QuerySet[Model] return type
instead of being forced to widen it to Iterable[Model]:

@strawberry_django.connection(DjangoCursorConnection[FruitType])
@staticmethod
def fruits() -> QuerySet[Fruit]:
    return Fruit.objects.all()

Previously this raised RelayWrongResolverAnnotationError because Django's
QuerySet[Model] collapses to the bare QuerySet class, which the relay
annotation check did not recognize as iterable.

This release was contributed by @​bellini666 in #​920

v0.86.2

Compare Source

Resolving a Relay node's id no longer goes through sync_to_async on every call.
resolve_id/resolve_id_attr now read the primary key directly off the in-memory
instance, removing an unnecessary thread hop (and contextvars copy) in async contexts.
The deferred-field fallback still bridges database access safely.

This release was contributed by @​bellini666 in #​921

v0.86.1

Compare Source

Fix offset_paginated fields applying the filter pipeline twice per resolution.

StrawberryOffsetPaginatedExtension.resolve forwards filters/order/pagination
to the inner resolver (so extensions and custom resolvers can access them), but then
re-applied them on the queryset the resolver returned. Filters, permission filtering
and the optimizer pass all ran twice; for a filter spanning a multivalued relation
the second .filter() duplicated the relation JOINs, which can grow the intermediate
row count quadratically and turn a sub-second query into a multi-minute one.

The queryset returned by the inner resolver is now passed straight to
resolve_paginated, matching the behavior of relay connection fields.

This release was contributed by @​aprams in #​916

v0.86.0

Compare Source

DateFilterLookup, TimeFilterLookup and DatetimeFilterLookup no longer require a type parameter, matching StrFilterLookup. The generated GraphQL input names also lose their type prefix (e.g. DateDateFilterLookup becomes DateFilterLookup).

@strawberry_django.filter_type(models.Project)
class ProjectFilter:
    due_date: strawberry_django.DateFilterLookup | None

Migrating:

• Drop the type argument from StrFilterLookup[str], DateFilterLookup[datetime.date], etc. The bare lookup now works; the bracket form still resolves to the same class but emits a DeprecationWarning.
• DatetimeFilterLookup.date and .time now accept Date / Time values (previously typed as Int, which never matched Django's __date / __time transforms).
• TimeFilterLookup.date and .time were removed. Django's __date / __time transforms don't apply to TimeField.

This release was contributed by @​bellini666 in #​910

v0.85.0

Compare Source

Breaking change: PAGINATION_MAX_LIMIT now defaults to 100 instead of None, so clients can
no longer request more than 100 rows in a single page by default.

Previously, the cap was off and PAGINATION_DEFAULT_LIMIT only applied when the client omitted the
limit, which let any client send limit: 9999999 and receive the full table in one response.

To restore the old behavior, set PAGINATION_MAX_LIMIT to None in STRAWBERRY_DJANGO
(not recommended for production).

This release was contributed by @​bellini666 in #​909

Additional contributors: @​Copilot

v0.84.0

Compare Source

Propagate child-type only= hints through method resolvers that declare the
relation via select_related. Previously they were silently dropped, causing
deferred loads or KeyErrors on descriptors without a deferred-load fallback
(e.g. djmoney.MoneyField) once the parent's select_related reached past a
single hop.

@strawberry_django.type(Child)
class ChildType:
    @strawberry_django.field(only=["extra_data"])
    def extra(self) -> str:
        return self.extra_data

@strawberry_django.type(Parent)
class ParentType:
    @strawberry_django.field(select_related=["child", "child__site"])
    def child(self) -> ChildType | None:
        return self.child

child.extra_data is now included in the parent's first SELECT.

This release was contributed by @​bellini666 in #​905

v0.83.0

Compare Source

Drop support for Django 4.2.

• Django 4.2 will reach end of support on April 30, 2026. check here

Drop support for Django 5.0.

• Django 5.0 has reached end of support on April 2, 2025. See https://endoflife.date/django

Drop support for Django 5.1.

• Django 5.1 has reached end of support on December 2, 2025. See https://endoflife.date/django

This release was contributed by @​p-r-a-v-i-n in #​897

v0.82.1

Compare Source

Fix FieldError when using the optimizer with django-polymorphic models.

The optimizer now uses the CamelCase model name for polymorphic optimization hints (e.g., ArtProject___field instead of app_label__artproject___field). This ensures that django-polymorphic correctly handles mismatched optimization hints during the realization of mixed querysets by raising an AssertionError (which it catches) instead of an unhandled FieldError. This change also avoids potential name collisions with lowercase reverse relations in multi-table inheritance.

A polymorphic optional dependency extra has been added, which sets the lower limit version to 4.0.0. Install with pip install strawberry-graphql-django[polymorphic] to pull in django-polymorphic.

This release was contributed by @​valkrypton in #​894

Additional contributors: @​bellini666

v0.82.0

Compare Source

Fix FieldExtension arguments being silently lost on StrawberryDjangoField.

When a FieldExtension appended arguments to field.arguments in its apply() method, the arguments worked with strawberry.field but silently disappeared with strawberry_django.field. This was because the mixin chain (Pagination → Ordering → Filters → Base) created a new list on every .arguments access, so .append() mutated a temporary copy.

Added a caching arguments property to StrawberryDjangoField so that the first access computes and caches the full arguments list, and subsequent accesses (including .append() from extensions) operate on the same cached list.

This release was contributed by @​bellini666 in #​892

v0.81.0

Compare Source

Fix StrFilterLookup so it can be used without a type parameter (e.g., name: StrFilterLookup | None). Previously this raised TypeError: "StrFilterLookup" is generic, but no type has been passed at schema build time.

This release was contributed by @​bellini666 in #​891

v0.80.0

Compare Source

Add support for graphql-core 3.3.x alongside existing 3.2.x support.

The minimum supported version of strawberry-graphql has been increased to 0.310.1.
When using the graphql-core 3.3.x series, the minimum supported version is 3.3.0a12.

This release was contributed by @​bellini666 in #​850

v0.79.2

Compare Source

Fix docs example for process_filters custom filter method where prefix was missing a trailing __, causing Django FieldError. Also add a UserWarning in process_filters() when a non-empty prefix doesn't end with __ to help users catch this mistake early.

This release was contributed by @​Ckk3 in #​883

v0.79.1

Compare Source

Fix FK _id fields (e.g. color_id: auto) in input types failing with mutations.create(). Previously, prepare_create_update() didn't recognize FK attnames, causing the value to be silently dropped and full_clean() to fail. Now attname fields are mapped and their raw PK values are passed through directly.

This release was contributed by @​bellini666 in #​880

v0.79.0

Compare Source

Pass Info instead of GraphQLResolveInfo to callables provided in prefetch_related and annotate arguments of strawberry_django.field.

This is technically a breaking change because the argument type passed to these callables has changed. However, Info acts as a proxy for GraphQLResolveInfo and is compatible with the utilities typically used within prefetch or annotate functions, such as optimize.

This release was contributed by @​rcybulski1122012 in #​872

v0.78.0

Compare Source

Add skip_queryset_filter parameter to filter_field() for declaring virtual (non-filtering) fields on filter types.

Fields marked with skip_queryset_filter=True appear in the GraphQL input type but are not applied as database filters. They are accessible via self.<field> in custom filter methods, making them useful for passing parameters like thresholds or configuration values.

@strawberry_django.filter_type(models.Fruit)
class FruitFilter:
    min_similarity: float | None = strawberry_django.filter_field(
        default=0.3, skip_queryset_filter=True
    )

    @strawberry_django.filter_field
    def search(
        self, info: Info, queryset: QuerySet[models.Fruit], value: str, prefix: str
    ):
        if self.min_similarity is not None:
            queryset = queryset.annotate(
                similarity=TrigramSimilarity(f"{prefix}name", value)
            ).filter(similarity__gte=self.min_similarity)
        return queryset, Q()

This release was contributed by @​bellini666 in #​876

v0.77.0

Compare Source

Automatically inject FK fields into .only() on user-provided Prefetch querysets
when the only optimization is enabled.

This prevents N+1 queries caused by Django re-fetching the FK field needed to match
prefetched rows back to parent objects.

The optimizer now correctly resolves reverse relations by related_name and restricts
FK injection to ManyToOneRel, OneToOneRel, and GenericRelation.

This release was contributed by @​bellini666 in #​874

v0.76.2

Compare Source

Fix N+1 queries when using optimize() inside a Prefetch object with .only() optimization. The optimizer now correctly auto-adds the FK field needed by Django to match prefetched objects back to their parent.

This release was contributed by @​bellini666 in #​873

v0.76.1

Compare Source

Fix optimizer skipping optimization entirely for aliased fields. When a GraphQL query uses aliases for the same field (e.g., a: milestones { id } and b: milestones { id }), the optimizer now merges them into a single prefetch instead of skipping optimization, preventing N+1 queries.

Aliases with different arguments (e.g., a: issues(filters: {search: "Foo"}) and b: issues(filters: {search: "Bar"})) are still skipped, since a single prefetch cannot satisfy both filter sets and optimizing one would produce wrong results for the other.

This release was contributed by @​bellini666 in #​871

v0.76.0

Compare Source

Add native federation support via strawberry_django.federation module.

New decorators that combine strawberry_django functionality with Apollo Federation:

• strawberry_django.federation.type - Federation-aware Django type with auto-generated resolve_reference
• strawberry_django.federation.interface - Federation-aware Django interface
• strawberry_django.federation.field - Federation-aware Django field with directives like @external, @requires, @provides

Example usage:

import strawberry
import strawberry_django
from strawberry.federation import Schema

@strawberry_django.federation.type(models.Product, keys=["upc"])
class Product:
    upc: strawberry.auto
    name: strawberry.auto
    price: strawberry.auto
    # resolve_reference is automatically generated!

schema = Schema(query=Query)

The auto-generated resolve_reference methods support composite keys and multiple keys, and integrate with the query optimizer.

Note: This release requires strawberry-graphql>=0.303.0.

v0.75.3

Compare Source

Add support for strawberry-graphql 0.307.x.

Also, the deprecated asserts_errors parameter has been removed from test client query() methods. Use assert_no_errors instead.

This release was contributed by @​bellini666 in #​870

Additional contributors: @​Copilot

v0.75.2

Compare Source

Fixes compatibility with strawberry-graphql>=0.296.0 by ensuring proper Info type resolution.

Info is now imported at runtime and resolver arguments include explicit type annotations.
This aligns with the updated behavior where parameter injection is strictly type-hint based rather than name-based.

Before, resolvers relying on implicit name-based injection could fail under newer Strawberry versions.

After this change, resolvers work correctly with the stricter type-based injection system introduced in newer releases.

This release was contributed by @​daudln in #​866

Additional contributors: @​pre-commit-ci[bot]

v0.75.1

Compare Source

Fix DuplicatedTypeName errors when using FilterLookup[str] by:

• Exporting StrFilterLookup from the top-level strawberry_django module
• Adding a deprecation warning when using FilterLookup[str] or FilterLookup[uuid.UUID]
• Updating documentation to recommend using specific lookup types

Users should migrate from:

from strawberry_django import FilterLookup

@strawberry_django.filter_type(models.Fruit)
class FruitFilter:
    name: FilterLookup[str] | None

To:

from strawberry_django import StrFilterLookup

@strawberry_django.filter_type(models.Fruit)
class FruitFilter:
    name: StrFilterLookup | None

This release was contributed by @​bellini666 in #​851

v0.75.0

Compare Source

Adds support for Django-style relationship traversal in strawberry_django.field(field_name=...) using LOOKUP_SEP (__). You can now flatten related objects or scalar fields without custom resolvers.

Examples:

@strawberry_django.type(User)
class UserType:
    role: RoleType | None = strawberry_django.field(
        field_name="assigned_role__role",
    )

    role_name: str | None = strawberry_django.field(
        field_name="assigned_role__role__name",
    )

The traversal returns None if an intermediate relationship is None. Documentation and tests cover the new behavior, including optimizer query counts.

This release was contributed by @​bellini666 in #​852

v0.74.3

Compare Source

v0.74.2

Compare Source

Fix offset pagination extensions so they receive pagination, order, and filter
arguments consistently with connection fields. This allows extensions to inspect
filters for permission/validation while keeping resolvers tolerant of missing
params.

v0.74.1

Compare Source

Pagination pageInfo.limit now returns the actual limit applied (after defaults and max caps), not the raw request value.

For example, with PAGINATION_DEFAULT_LIMIT=20, PAGINATION_MAX_LIMIT=50:

{ fruits(pagination: { limit: null }) { pageInfo { limit } } }

Before:

{
  "data": {
    "fruits": {
      "pageInfo": {
        "limit": null
      }
    }
  }
}

After:

{
  "data": {
    "fruits": {
      "pageInfo": {
        "limit": 20
      }
    }
  }
}

Also fixes limit: null to use PAGINATION_DEFAULT_LIMIT instead of PAGINATION_MAX_LIMIT.

This release was contributed by @​bellini666 in #​848

v0.74.0

Compare Source

Add configurable PAGINATION_MAX_LIMIT setting to cap pagination requests, preventing clients from requesting unlimited data via limit: null or excessive limits.

This addresses security and performance concerns by allowing projects to enforce a maximum number of records that can be requested through pagination.

Configuration:

STRAWBERRY_DJANGO = {
    "PAGINATION_MAX_LIMIT": 1000,  # Cap all requests to 1000 records
}

When set, any client request with limit: null, negative limits, or limits exceeding the configured maximum will be capped to PAGINATION_MAX_LIMIT. Defaults to None (unlimited) for backward compatibility, though setting a limit is recommended for production environments.

Works with both offset-based and window-based pagination.

This release was contributed by @​bellini666 in #​847

v0.73.1

Compare Source

This release fixes a bug, which caused nested prefetch_related hints to get incorrectly merged
in certain cases.

This release was contributed by @​diesieben07 in #​839

v0.73.0

Compare Source

Nothing changed, testing the new release process using autopub.

v0.72.2

Compare Source

Nothing changed, testing the new release process using autopub.

This release was contributed by @​bellini666 in #​837

v0.72.0

Compare Source

v0.71.0

Compare Source

v0.70.1

Compare Source

v0.70.0

Compare Source

v0.69.0

Compare Source

v0.68.0

Compare Source

v0.67.2

Compare Source

v0.67.1

Compare Source

v0.67.0

Compare Source

v0.66.2

Compare Source

v0.66.1

Compare Source

v0.66.0

Compare Source

v0.65.1

Compare Source

v0.65.0

Compare Source

v0.64.0

Compare Source

v0.63.0

Compare Source

v0.62.0

Compare Source

v0.61.0

Compare Source

v0.60.0

Compare Source

v0.59.1

Compare Source

v0.59.0

Compare Source

v0.58.0

Compare Source

v0.57.1

Compare Source

v0.57.0

Compare Source

v0.56.0

Compare Source

v0.55.2

Compare Source

v0.55.1

Compare Source

v0.55.0

Compare Source

v0.54.0

Compare Source

v0.53.3

Compare Source

v0.53.2

Compare Source

v0.53.1

Compare Source

v0.53.0

Compare Source

v0.52.1

Compare Source

v0.52.0

Compare Source

v0.51.0

Compare Source

v0.50.0

Compare Source

v0.49.1

Compare Source

v0.49.0

Compare Source

v0.48.0

Compare Source

v0.47.2

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock

Using CPython 3.13.15 interpreter at: /opt/containerbase/tools/python/3.13.15/bin/python3.13
error: No solution found when resolving dependencies
  cause: Because strawberry-graphql-django>=0.89.2 depends on django>=5.2 and your project depends on django>=4.2,<4.3, we can conclude that strawberry-graphql-django>=0.89.2 and your project are incompatible.
         And because your project depends on strawberry-graphql-django==0.89.2, we can conclude that your project's requirements are unsatisfiable.