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

[renovate]

This PR contains the following updates:

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

---

Release Notes

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

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: 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.