Sourced from strawberry-graphql's releases.

🍓 0.307.1

This release fixes issues with explicit field definitions in experimental pydantic types:

all_fields=True now respects explicit field definitions: Previously, using all_fields=True would override any explicitly defined fields in the strawberry type. Now, explicit definitions take precedence, allowing you to:

• Mark fields as strawberry.Private to hide them from the GraphQL schema
• Add field extensions (e.g., for authentication, caching, transformations)
• Override field types
• Add custom resolvers

The warning "Using all_fields overrides any explicitly defined fields" has been removed since combining all_fields=True with explicit definitions is now a valid and useful pattern.

Private fields are auto-populated from pydantic models: When a strawberry.Private field has the same name as a pydantic model field, from_pydantic() will automatically populate it from the model (can be overridden via the extra dict).

Example:

from pydantic import BaseModel
import strawberry
from strawberry.experimental.pydantic import type as pyd_type
from strawberry.extensions.field_extension import FieldExtension
class MaskExtension(FieldExtension):
def resolve(self, next_, source, info, **kwargs):
result = next_(source, info, **kwargs)
return result[:3] + "****" if result else result
class UserModel(BaseModel):
name: str
email: str
password: str
@​pyd_type(model=UserModel, all_fields=True)
class User:
# Add extension to mask email in responses
email: str = strawberry.field(extensions=[MaskExtension()])
# Hide password from GraphQL schema entirely
password: strawberry.Private[str]
name and email are exposed in schema, password is not
email will be masked by the extension
pydantic_user = UserModel(name="Alice", email="alice@example.com", password="secret")
strawberry_user = User.from_pydantic(pydantic_user)
Private field is still accessible internally
print(strawberry_user.password)  # "secret"
</tr></table>

... (truncated)

Sourced from strawberry-graphql's changelog.

0.307.1 - 2026-02-24

This release fixes issues with explicit field definitions in experimental pydantic types:

all_fields=True now respects explicit field definitions: Previously, using all_fields=True would override any explicitly defined fields in the strawberry type. Now, explicit definitions take precedence, allowing you to:

• Mark fields as strawberry.Private to hide them from the GraphQL schema
• Add field extensions (e.g., for authentication, caching, transformations)
• Override field types
• Add custom resolvers

The warning "Using all_fields overrides any explicitly defined fields" has been removed since combining all_fields=True with explicit definitions is now a valid and useful pattern.

Private fields are auto-populated from pydantic models: When a strawberry.Private field has the same name as a pydantic model field, from_pydantic() will automatically populate it from the model (can be overridden via the extra dict).

Example:

from pydantic import BaseModel
import strawberry
from strawberry.experimental.pydantic import type as pyd_type
from strawberry.extensions.field_extension import FieldExtension
class MaskExtension(FieldExtension):
def resolve(self, next_, source, info, **kwargs):
result = next_(source, info, **kwargs)
return result[:3] + "****" if result else result
class UserModel(BaseModel):
name: str
email: str
password: str
@​pyd_type(model=UserModel, all_fields=True)
class User:
# Add extension to mask email in responses
email: str = strawberry.field(extensions=[MaskExtension()])
# Hide password from GraphQL schema entirely
password: strawberry.Private[str]
name and email are exposed in schema, password is not
email will be masked by the extension
pydantic_user = UserModel(name="Alice", email="alice@example.com", password="secret")
strawberry_user = User.from_pydantic(pydantic_user)
</tr></table>

... (truncated)

• e0764c2 Release 🍓 0.307.1
• 1b5d199 Allow strawberry.auto to override all_fields=True | Allow Private Fields to w...
• eae8995 Release 🍓 0.307.0
• 3b15ec9 Remove deprecated _type_definition and _enum_definition aliases (#4219)
• 2c9bc4b [pre-commit.ci] pre-commit autoupdate (#4266)
• ab4def9 ci(deps): bump github/codeql-action from 4.32.3 to 4.32.4 (#4261)
• 012b369 ci(deps): bump actions/checkout from 4.3.1 to 6.0.2 (#4262)
• 1aef9b9 deps(python)(deps-dev): bump the all-dependencies group with 4 updates (#4264)
• 438fe2c deps(e2e)(deps): bump lucide-react from 0.564.0 to 0.575.0 in /e2e (#4263)
• 8f739e0 deps(python)(deps): bump wheel from 0.45.1 to 0.46.2 (#4265)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)