NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI, #1553 most downloaded on PyPI
A library for creating GraphQL APIs
Latest stable
0.341.2
Last release 12 days ago
07 Nov 2026
Ships fairly regularly
a new release about every 1 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
1155 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
This release fixes an issue where DuplicatedTypeName exception would be raised for nested generics like in the example below:
This release fixes an issue where DuplicatedTypeName exception would be raised
for nested generics like in the example below:
from typing import Generic, TypeVar
import strawberry
T = TypeVar("T")
@strawberry.type
class Wrapper(Generic[T]):
value: T
@strawberry.type
class Query:
a: Wrapper[Wrapper[int]]
b: Wrapper[Wrapper[int]]
schema = strawberry.Schema(query=Query)
This piece of code and similar ones will now work correctly.
Releases contributed by @bellini666 via #3946
This release fixes an issue where DuplicatedTypeName exception would be raised
for nested generics like in the example below:
from typing import Generic, TypeVar
import strawberry
T = TypeVar("T")
@strawberry.type
class Wrapper(Generic[T]):
value: T
@strawberry.type
class Query:
a: Wrapper[Wrapper[int]]
b: Wrapper[Wrapper[int]]
schema = strawberry.Schema(query=Query)
This piece of code and similar ones will now work correctly.
Contributed by Thiago Bellini Ribeiro via PR #3946
Your coding agent can read these notes before it upgrades. Set up the MCP server →
This release fixes NameConverter to properly handle lazy types.
This release fixes NameConverter to properly handle lazy types.
Releases contributed by @rcybulski1122012 via #3944
This release fixes NameConverter to properly handle lazy types.
Contributed by Radosław Cybulski via PR #3944
Nothing published for this version
Nothing published for this version
This release adds support for lazy types in ConnectionExtension.
This release adds support for lazy types in ConnectionExtension.
Releases contributed by @rcybulski1122012 via #3941
This release adds support for lazy types in ConnectionExtension.
Contributed by Radosław Cybulski via PR #3941
In this release, we updated Strawberry to gracefully handle requests containing an invalid extensions parameter. Previously, such requests could resul
In this release, we updated Strawberry to gracefully handle requests containing
an invalid extensions parameter. Previously, such requests could result in
internal server errors. Now, Strawberry will return a 400 Bad Request response
with a clear error message, conforming to the GraphQL over HTTP specification.
Releases contributed by @DoctorJohn via #3943
In this release, we updated Strawberry to gracefully handle requests containing
an invalid extensions parameter. Previously, such requests could result in
internal server errors. Now, Strawberry will return a 400 Bad Request response
with a clear error message, conforming to the GraphQL over HTTP specification.
Contributed by Jonathan Ehwald via PR #3943
This release improves performance of argument conversion for lists of primitives.
This release improves performance of argument conversion for lists of primitives.
Releases contributed by @blothmann via #3773
This release improves performance of argument conversion for lists of primitives.
In this release, we updated Strawberry to gracefully handle requests containing an invalid variables parameter. Previously, such requests could result
In this release, we updated Strawberry to gracefully handle requests containing
an invalid variables parameter. Previously, such requests could result in
internal server errors. Now, Strawberry will return a 400 Bad Request response
with a clear error message, conforming to the GraphQL over HTTP specification.
Releases contributed by @DoctorJohn via #3932
In this release, we updated Strawberry to gracefully handle requests containing
an invalid variables parameter. Previously, such requests could result in
internal server errors. Now, Strawberry will return a 400 Bad Request response
with a clear error message, conforming to the GraphQL over HTTP specification.
Contributed by Jonathan Ehwald via PR #3932
In this release, we updated Strawberry to gracefully handle requests containing an invalid query parameter. Previously, such requests could result in
In this release, we updated Strawberry to gracefully handle requests containing
an invalid query parameter. Previously, such requests could result in internal
server errors, but now they will return a 400 Bad Request response with an
appropriate error message, conforming to the GraphQL over HTTP specification.
Releases contributed by @DoctorJohn via #3927
In this release, we updated Strawberry to gracefully handle requests containing
an invalid query parameter. Previously, such requests could result in internal
server errors, but now they will return a 400 Bad Request response with an
appropriate error message, conforming to the GraphQL over HTTP specification.
Contributed by Jonathan Ehwald via PR #3927
Fixes a bug that caused merged unions with duplicated entries to fail the schema validation when merging two strawberry.union types.
Fixes a bug that caused merged unions with duplicated entries to fail the schema validation when merging two
strawberry.union types.
Releases contributed by @erikwrede via #3923
Fixes a bug that caused merged unions with duplicated entries to fail the schema validation when merging two
strawberry.union types.
Contributed by Erik Wrede via PR #3923
In this release, we updated the aiohttp integration to handle aiohttp.ClientConnectionResetErrors, which can occur when a WebSocket connection is unex
In this release, we updated the aiohttp integration to handle
aiohttp.ClientConnectionResetErrors, which can occur when a WebSocket
connection is unexpectedly closed, gracefully.
Releases contributed by @DoctorJohn via #3922
In this release, we updated the aiohttp integration to handle
aiohttp.ClientConnectionResetErrors, which can occur when a WebSocket
connection is unexpectedly closed, gracefully.
Contributed by Jonathan Ehwald via PR #3922
Adds a new CLI command strawberry locate-definition that allows you to find the source location of a definition in the schema.
Adds a new CLI command strawberry locate-definition that allows you to find the source location of a definition in the schema.
strawberry locate-definition path.to.schema:schema ObjectName
strawberry locate-definition path.to.schema:schema ObjectName.fieldName
Results take the form of path/to/file.py:line:column, for example: src/models/user.py:45:12.
This can be used, for example, with the go to definition feature of VS Code's Relay extension (configured via the relay.pathToLocateCommand setting).
Releases contributed by @millar via #3902
This release adds compatibility with LibCST v1.8
This release adds compatibility with LibCST v1.8
Releases contributed by @patrick91 via #3921
This release adds compatibility with LibCST v1.8
Contributed by Patrick Arminio via PR #3921
Introduces an optional operation_extensions parameter throughout the GraphQL execution flow—adding it to execution entry points and embedding it into
Introduces an optional operation_extensions parameter throughout the GraphQL execution flow—adding it to execution entry points and embedding it into the ExecutionContext—so custom extensions can access per-operation metadata.
Releases contributed by @mdgilene via #3878
Introduces an optional operation_extensions parameter throughout the GraphQL execution flow—adding it to execution entry points and embedding it into the ExecutionContext—so custom extensions can access per-operation metadata.
Contributed by Matt Gilene via PR #3878
This release fixes an issue that caused schema generation with Maybe to fail when using lists, such as Maybe[List[User]].
This release fixes an issue that caused schema generation with Maybe to fail when using lists, such as Maybe[List[User]].
Releases contributed by @erikwrede via #3920
This release fixes an issue that caused schema generation with Maybe to fail when using lists, such as Maybe[List[User]].
Contributed by Erik Wrede via PR #3920
In this release, we fixed various edge cases around operation selection in GraphQL documents. Now, operation selection works consistently across all p
In this release, we fixed various edge cases around operation selection in GraphQL documents. Now, operation selection works consistently across all protocols, both in documents with single and multiple operations.
Releases contributed by @DoctorJohn via #3916
In this release, we fixed various edge cases around operation selection in GraphQL documents. Now, operation selection works consistently across all protocols, both in documents with single and multiple operations.
Contributed by Jonathan Ehwald via PR #3916
In this release, we updated the type hints for subscription_protocols across all HTTP view integrations. It's now consistently defined as Sequence[str
In this release, we updated the type hints for subscription_protocols across
all HTTP view integrations. It's now consistently defined as Sequence[str],
the minimum type required by Strawberry.
Releases contributed by @DoctorJohn via #3910
In this release, we updated the type hints for subscription_protocols across
all HTTP view integrations. It's now consistently defined as Sequence[str],
the minimum type required by Strawberry.
Contributed by Jonathan Ehwald via PR #3910
In this release, we replaced the usage of an undocumented AIOHTTP MultipartReader API with the intended public API.
In this release, we replaced the usage of an undocumented AIOHTTP
MultipartReader API with the intended public API.
Releases contributed by @DoctorJohn via #3906
In this release, we replaced the usage of an undocumented AIOHTTP
MultipartReader API with the intended public API.
Contributed by Jonathan Ehwald via PR #3906
This release fixes that the Chalice HTTP view integration did not set appropriate content-type headers for responses, as it's recommended by the Graph
This release fixes that the Chalice HTTP view integration did not set appropriate content-type headers for responses, as it's recommended by the GraphQL over HTTP specification.
Releases contributed by @DoctorJohn via #3904
This release fixes that the Chalice HTTP view integration did not set appropriate content-type headers for responses, as it's recommended by the GraphQL over HTTP specification.
Contributed by Jonathan Ehwald via PR #3904
Starting with this release, Strawberry will throw an error if one of your input types tries to inherit from one or more interfaces. This new error enf
Starting with this release, Strawberry will throw an error if one of your input types tries to inherit from one or more interfaces. This new error enforces the GraphQL specification that input types cannot implement interfaces.
The following code, for example, will now throw an error:
import strawberry
@strawberry.interface
class SomeInterface:
some_field: str
@strawberry.input
class SomeInput(SomeInterface):
another_field: int
Releases contributed by @scratchmex via #1254
This release modifies export-schema cli to include an EOF newline if --output option is provided. This allows better review in github.com for the gene
This release modifies export-schema cli to include an EOF newline if --output option is provided. This allows better review in github.com for the generated schema files.
Releases contributed by @yunkaiz via #3896
This release modifies export-schema cli to include an EOF newline if --output option is provided. This allows better review in github.com for the generated schema files.
Contributed by Yunkai Zhou via PR #3896
This release features a dedicated extension to disable introspection queries. Disabling introspection queries was already possible using the AddValida
This release features a dedicated extension to disable introspection queries.
Disabling introspection queries was already possible using the
AddValidationRules extension. However, using this new extension requires fewer
steps and makes the feature more discoverable.
import strawberry
from strawberry.extensions import DisableIntrospection
@strawberry.type
class Query:
@strawberry.field
def hello(self) -> str:
return "Hello, world!"
schema = strawberry.Schema(
Query,
extensions=[
DisableIntrospection(),
],
)
Releases contributed by @DoctorJohn via #3895
This release fixes an AttributeError that occurred when a fragment and an OperationDefinitionNode shared the same name, and the fragment appeared firs
This release fixes an AttributeError that occurred when a fragment and an OperationDefinitionNode shared the same name, and the fragment appeared first in the document.
The following example will now work as expected:
fragment UserAgent on UserAgentType {
id
}
query UserAgent {
userAgent {
...UserAgent
}
}
Releases contributed by @pre-commit-ci[bot] via #3893
This release fixes an AttributeError that occurred when a fragment and an OperationDefinitionNode shared the same name, and the fragment appeared first in the document.
The following example will now work as expected:
fragment UserAgent on UserAgentType {
id
}
query UserAgent {
userAgent {
...UserAgent
}
}
This Release contains fix of enum value was not working in generic container in lazy union.
This Release contains fix of enum value was not working in generic container in lazy union.
Releases contributed by @benzolium via #3883
This Release contains fix of enum value was not working in generic container in lazy union.
Added a new configuration option _unsafe_disable_same_type_validation that allows disabling the same type validation check in the schema converter. Th
Added a new configuration option _unsafe_disable_same_type_validation that allows disabling the same type validation check in the schema converter. This is useful in cases where you need to have multiple type definitions with the same name in your schema.
Example:
@strawberry.type(name="DuplicatedType")
class A:
a: int
@strawberry.type(name="DuplicatedType")
class B:
b: int
schema = strawberry.Schema(
query=Query,
types=[A, B],
config=strawberry.StrawberryConfig(_unsafe_disable_same_type_validation=True),
)
Note: This is an unsafe option and should be used with caution as it bypasses a safety check in the schema converter.
Releases contributed by @narmatov-asylbek via #3887
This release fixes that the create_type tool asked users to pass a name for fields without resolvers even when a name was already provided.
This release fixes that the create_type tool asked users to pass a name for
fields without resolvers even when a name was already provided.
The following code now works as expected:
import strawberry
from strawberry.tools import create_type
first_name = strawberry.field(name="firstName")
Query = create_type(f"Query", [first_name])
Releases contributed by @DoctorJohn via #3885
This release fixes that the create_type tool asked users to pass a name for
fields without resolvers even when a name was already provided.
The following code now works as expected:
import strawberry
from strawberry.tools import create_type
first_name = strawberry.field(name="firstName")
Query = create_type(f"Query", [first_name])
Contributed by Jonathan Ehwald via PR #3885
In this release, we improved some GraphQL over WS error messages. More precise error messages are now returned if Strawberry fails to find an operatio
In this release, we improved some GraphQL over WS error messages. More precise error messages are now returned if Strawberry fails to find an operation in the query document.
Releases contributed by @DoctorJohn via #3869
In this release, we improved some GraphQL over WS error messages. More precise error messages are now returned if Strawberry fails to find an operation in the query document.
Contributed by Jonathan Ehwald via PR #3869
This release fixes that the Strawberry debug server no longer supported WebSockets out of the box.
This release fixes that the Strawberry debug server no longer supported WebSockets out of the box.
Releases contributed by @DoctorJohn via #3872
This release fixes that the Strawberry debug server no longer supported WebSockets out of the box.
Contributed by Jonathan Ehwald via PR #3872
This release fixes an dependency issue with the Strawberry CLI and libcst.
This release fixes an dependency issue with the Strawberry CLI and libcst.
Releases contributed by @DoctorJohn via #3875
This release fixes an dependency issue with the Strawberry CLI and libcst.
Contributed by Jonathan Ehwald via PR #3875
This release resolves the issue of subscriptions started via the legacy graphql-ws WebSocket subprotocol getting stuck if a non-existing operationName
This release resolves the issue of subscriptions started via the legacy graphql-ws WebSocket subprotocol getting stuck if a non-existing operationName was specified.
Releases contributed by @DoctorJohn via #3858
This release resolves the issue of subscriptions started via the legacy graphql-ws WebSocket subprotocol getting stuck if a non-existing operationName was specified.
Contributed by Jonathan Ehwald via PR #3858
Fix multipart subscriptions by always yielding the closing boundary if it's enqueued.
Fix multipart subscriptions by always yielding the closing boundary if it's enqueued.
Releases contributed by @RogerHYang via #3866
Fix multipart subscriptions by always yielding the closing boundary if it's enqueued.
Contributed by Roger Yang via PR #3866
This release adds support for GraphQL over WebSocket transport protocols to the Quart integration.
This release adds support for GraphQL over WebSocket transport protocols to the Quart integration.
Releases contributed by @DoctorJohn via #3860
This release adds support for GraphQL over WebSocket transport protocols to the Quart integration.
Contributed by Jonathan Ehwald via PR #3860
This release adds support for input extension (To explain and document)
This release adds support for input extension (To explain and document)
Releases contributed by @omarzouk via #3461
This release adds support for input extension (To explain and document)
Contributed by Omar Marzouk via PR #3461
Nothing published for this version
Nothing published for this version
This release (finally) fixes support for using ID and GlobalID in the same schema.
This release (finally) fixes support for using ID and GlobalID
in the same schema.
Releases contributed by @patrick91 via #3859
This release (finally) fixes support for using ID and GlobalID
in the same schema.
Contributed by Patrick Arminio via PR #3859
Nothing published for this version
This releases fixed an issue that prevented from using ID and GlobalID at the same time, like in this example:
This releases fixed an issue that prevented from using ID and GlobalID at the same
time, like in this example:
import strawberry
from strawberry.relay.types import GlobalID
@strawberry.type
class Query:
@strawberry.field
def hello(self, id: GlobalID) -> str:
return "Hello World"
@strawberry.field
def hello2(self, id: strawberry.ID) -> str:
return "Hello World"
schema = strawberry.Schema(
Query,
)
Releases contributed by @patrick91 via #3855
This releases fixed an issue that prevented from using ID and GlobalID at the same
time, like in this example:
import strawberry
from strawberry.relay.types import GlobalID
@strawberry.type
class Query:
@strawberry.field
def hello(self, id: GlobalID) -> str:
return "Hello World"
@strawberry.field
def hello2(self, id: strawberry.ID) -> str:
return "Hello World"
schema = strawberry.Schema(
Query,
)
Contributed by Patrick Arminio via PR #3855
This release renames the generated type from GlobalID to ID in the GraphQL schema.
This release renames the generated type from GlobalID to ID in the GraphQL
schema.
This means that when using relay.Node, like in this example:
@strawberry.type
class Fruit(relay.Node):
code: relay.NodeID[int]
name: str
You'd create a GraphQL type that looks like this:
type Fruit implements Node {
id: ID!
name: String!
}
while previously you'd get this:
type Fruit implements Node {
id: GlobalID!
name: String!
}
The runtime behaviour is still the same, so if you want to use GlobalID in
Python code, you can still do so, for example:
@strawberry.type
class Mutation:
@strawberry.mutation
@staticmethod
async def update_fruit_weight(id: relay.GlobalID, weight: float) -> Fruit:
# while `id` is a GraphQL `ID` type, here is still an instance of `relay.GlobalID`
fruit = await id.resolve_node(info, ensure_type=Fruit)
fruit.weight = weight
return fruit
If you want to revert this change, and keep GlobalID in the schema, you can
use the following configuration:
schema = strawberry.Schema(
query=Query, config=StrawberryConfig(relay_use_legacy_global_id=True)
)
Releases contributed by @patrick91 via #3853
This release adds support to use strawberry.Parent with future annotations.
This release adds support to use strawberry.Parent with future annotations.
For example, the following code will now work as intended:
from __future__ import annotations
def get_full_name(user: strawberry.Parent[User]) -> str:
return f"{user.first_name} {user.last_name}"
@strawberry.type
class User:
first_name: str
last_name: str
full_name: str = strawberry.field(resolver=get_full_name)
@strawberry.type
class Query:
@strawberry.field
def user(self) -> User:
return User(first_name="John", last_name="Doe")
schema = strawberry.Schema(query=Query)
Or even when not using future annotations, but delaying the evaluation of User, like:
# Note the User being delayed by passing it as a string
def get_full_name(user: strawberry.Parent["User"]) -> str:
return f"{user.first_name} {user.last_name}"
@strawberry.type
class User:
first_name: str
last_name: str
full_name: str = strawberry.field(resolver=get_full_name)
@strawberry.type
class Query:
@strawberry.field
def user(self) -> User:
return User(first_name="John", last_name="Doe")
schema = strawberry.Schema(query=Query)
Releases contributed by @bellini666 via #3851
Nothing published for this version
This release adds a new (preferable) way to handle optional updates. Up until now when you wanted to inffer if an input value was null or absent you'd
This release adds a new (preferable) way to handle optional updates. Up until
now when you wanted to inffer if an input value was null or absent you'd use
strawberry.UNSET which is a bit cumbersome and error prone.
Now you can use strawberry.Maybe to identify if a
value was provided or not.
e.g.
import strawberry
@strawberry.type
class User:
name: str
phone: str | None
@strawberry.input
class UpdateUserInput:
name: str
phone: strawberry.Maybe[str]
@strawberry.type
class Mutation:
def update_user(self, input: UpdateUserInput) -> None:
reveal_type(input.phone) # strawberry.Some[str | None] | None
if input.phone:
reveal_type(input.phone.value) # str | None
update_user_phone(input.phone.value)
Or, if you can use pattern matching:
@strawberry.type
class Mutation:
def update_user(self, input: UpdateUserInput) -> None:
match input.phone:
case strawberry.Some(value=value):
update_user_phone(input.phone.value)
You can also use strawberry.Maybe as a field argument like so
import strawberry
@strawberry.field
def filter_users(self, phone: strawberry.Maybe[str] = None) -> list[User]:
if phone:
return filter_users_by_phone(phone.value)
return get_all_users()
Releases contributed by @nrbnlulu via #3791
This release adds support for custom names in enum values using the name parameter in strawberry.enum_value.
This release adds support for custom names in enum values using the name parameter in strawberry.enum_value.
This allows you to specify a different name for an enum value in the GraphQL schema while keeping the original Python enum member name. For example:
@strawberry.enum
class IceCreamFlavour(Enum):
VANILLA = "vanilla"
CHOCOLATE_COOKIE = strawberry.enum_value("chocolate", name="chocolateCookie")
This will produce a GraphQL schema with the custom name:
enum IceCreamFlavour {
VANILLA
chocolateCookie
}
Releases contributed by @patrick91 via #3841
Nothing published for this version
Fix bug where files would be converted into io.BytesIO when using the sanic GraphQLView instead of using the sanic File type
Fix bug where files would be converted into io.BytesIO when using the sanic GraphQLView instead of using the sanic File type
Releases contributed by @Maypher via #3751
Fix bug where files would be converted into io.BytesIO when using the sanic GraphQLView instead of using the sanic File type
This release adds support for using strawberry.union with generics, like in this example:
This release adds support for using strawberry.union with generics, like in this example:
@strawberry.type
class ObjectQueries[T]:
@strawberry.field
def by_id(
self, id: strawberry.ID
) -> Union[T, Annotated[NotFoundError, strawberry.union("ByIdResult")]]: ...
@strawberry.type
class Query:
@strawberry.field
def some_type_queries(self, id: strawberry.ID) -> ObjectQueries[SomeType]: ...
which, now, creates a correct union type named SomeTypeByIdResult
Releases contributed by @enoua5 via #3515
This release adds support for using strawberry.union with generics, like in this example:
@strawberry.type
class ObjectQueries[T]:
@strawberry.field
def by_id(
self, id: strawberry.ID
) -> Union[T, Annotated[NotFoundError, strawberry.union("ByIdResult")]]: ...
@strawberry.type
class Query:
@strawberry.field
def some_type_queries(self, id: strawberry.ID) -> ObjectQueries[SomeType]: ...
which, now, creates a correct union type named SomeTypeByIdResult
Contributed by Jacob Allen via PR #3515
Change pydantic conversion to not load field data unless requested
Change pydantic conversion to not load field data unless requested
Releases contributed by @Mark90 via #3812
Change pydantic conversion to not load field data unless requested
This releases improves support for relay.Edge subclasses.
This releases improves support for relay.Edge subclasses.
resolve_edge now accepts **kwargs, so custom fields can be added to your edge classes without wholly
replacing resolve_edge:
@strawberry.type(name="Edge", description="An edge in a connection.")
class CustomEdge(relay.Edge[NodeType]):
index: int
@classmethod
def resolve_edge(cls, node: NodeType, *, cursor: Any = None, **kwargs: Any) -> Self:
assert isinstance(cursor, int)
return super().resolve_edge(node, cursor=cursor, index=cursor, **kwargs)
You can also specify a custom cursor prefix, in case you want to implement a different
kind of cursor than a plain ListConnection:
@strawberry.type(name="Edge", description="An edge in a connection.")
class CustomEdge(relay.Edge[NodeType]):
CURSOR_PREFIX: ClassVar[str] = "mycursor"
Releases contributed by @diesieben07 via #3836
This release contains a few improvements to how AsyncGenerators are handled by strawberry codebase, ensuring they get properly closed in case of unexp
This release contains a few improvements to how AsyncGenerators are handled by
strawberry codebase, ensuring they get properly closed in case of unexpected
errors.
Releases contributed by @bellini666 via #3834
This release contains a few improvements to how AsyncGenerators are handled by
strawberry codebase, ensuring they get properly closed in case of unexpected
errors.
Contributed by Thiago Bellini Ribeiro via PR #3834
This releases add support for passing in a custom TracerProvider to the OpenTelemetryExtension.
This releases add support for passing in a custom TracerProvider to the OpenTelemetryExtension.
Releases contributed by @cdorsey via #3830
This releases add support for passing in a custom TracerProvider to the OpenTelemetryExtension.
Contributed by Chase Dorsey via PR #3830
Adds the ability to include pydantic computed fields when using pydantic.type decorator.
Adds the ability to include pydantic computed fields when using pydantic.type decorator.
Example:
class UserModel(pydantic.BaseModel):
age: int
@computed_field
@property
def next_age(self) -> int:
return self.age + 1
@strawberry.experimental.pydantic.type(
UserModel, all_fields=True, include_computed=True
)
class User:
pass
Will allow nextAge to be requested from a user entity.
Releases contributed by @tylernisonoff via #3798
Adds the ability to include pydantic computed fields when using pydantic.type decorator.
Example:
class UserModel(pydantic.BaseModel):
age: int
@computed_field
@property
def next_age(self) -> int:
return self.age + 1
@strawberry.experimental.pydantic.type(
UserModel, all_fields=True, include_computed=True
)
class User:
pass
Will allow nextAge to be requested from a user entity.
Contributed by Tyler Nisonoff via PR #3798
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This release updates the Content-Type header from "text/html" to "text/html; charset=utf-8" to prevent the GraphQL IDE from displaying unusual or in
This release updates the Content-Type header from "text/html" to "text/html; charset=utf-8" to prevent the GraphQL IDE from displaying unusual or incorrect characters.
Releases contributed by @moritz89 via #3824
This release updates the Content-Type header from "text/html" to "text/html; charset=utf-8" to prevent the GraphQL IDE from displaying unusual or incorrect characters.
Contributed by Moritz Ulmer via PR #3824
This release updates the internals of our subscription implementation, to make the code easier to maintain for future changes.
This release updates the internals of our subscription implementation, to make the code easier to maintain for future changes.
Releases contributed by @patrick91 via #3787
This release updates the internals of our subscription implementation, to make the code easier to maintain for future changes.
Contributed by Patrick Arminio via PR #3787
This release adds support for the upcoming version of Pydantic (2.11)
This release adds support for the upcoming version of Pydantic (2.11)
Releases contributed by @patrick91 via #3808
This release adds support for the upcoming version of Pydantic (2.11)
Contributed by Patrick Arminio via PR #3808
This release changes the required version of packaging from >=24 to >=23, in order to allow using Strawberry on https://play.strawberry.rocks
This release changes the required version of packaging from >=24 to >=23, in order to allow using Strawberry on https://play.strawberry.rocks
Releases contributed by @patrick91 via #3806
This release changes the required version of packaging from >=24 to >=23, in order to allow using Strawberry on https://play.strawberry.rocks
Contributed by Patrick Arminio via PR #3806
One column per quarter.