🍓 0.275.5

This release improves performance of argument conversion for lists of primitives.

Releases contributed by @blothmann via #3773

🍓 0.275.4

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

🍓 0.275.3

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

🍓 0.275.2

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

🍓 0.275.1

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

🍓 0.275.0

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

🍓 0.274.3

This release adds compatibility with LibCST v1.8

Releases contributed by @patrick91 via #3921

🍓 0.274.2

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

🍓 0.274.1

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

🍓 0.274.0

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