build(deps): bump strawberry-graphql from 0.240.0 to 0.243.0 in the pip group

[dependabot]

Bumps the pip group with 1 update: strawberry-graphql.

Updates strawberry-graphql from 0.240.0 to 0.243.0

Release notes

Sourced from strawberry-graphql's releases.

🍓 0.243.0

Starting with this release, multipart uploads are disabled by default and Strawberry Django view is no longer implicitly exempted from Django's CSRF protection. Both changes relieve users from implicit security implications inherited from the GraphQL multipart request specification which was enabled in Strawberry by default.

These are breaking changes if you are using multipart uploads OR the Strawberry Django view. Migrations guides including further information are available on the Strawberry website.

Releases contributed by @​DoctorJohn via #3645

🍓 0.242.0

Starting with this release, clients using the legacy graphql-ws subprotocol will receive an error when they try to send binary data frames. Before, binary data frames were silently ignored.

While vaguely defined in the protocol, the legacy graphql-ws subprotocol is generally understood to only support text data frames.

Releases contributed by @​DoctorJohn via #3633

🍓 0.241.0

You can now configure your schemas to provide a custom subclass of strawberry.types.Info to your types and queries.

import strawberry
from strawberry.schema.config import StrawberryConfig
from .models import ProductModel
class CustomInfo(strawberry.Info):
@​property
def selected_group_id(self) -> int | None:
"""Get the ID of the group you're logged in as."""
return self.context["request"].headers.get("Group-ID")
@​strawberry.type
class Group:
id: strawberry.ID
name: str
@​strawberry.type
class User:
id: strawberry.ID
name: str
group: Group
@​strawberry.type
class Query:
</tr></table>

... (truncated)

Changelog

Sourced from strawberry-graphql's changelog.

0.243.0 - 2024-09-25

Starting with this release, multipart uploads are disabled by default and Strawberry Django view is no longer implicitly exempted from Django's CSRF protection. Both changes relieve users from implicit security implications inherited from the GraphQL multipart request specification which was enabled in Strawberry by default.

These are breaking changes if you are using multipart uploads OR the Strawberry Django view. Migrations guides including further information are available on the Strawberry website.

Contributed by Jonathan Ehwald via [PR #3645](strawberry-graphql/strawberry#3645)

0.242.0 - 2024-09-19

Starting with this release, clients using the legacy graphql-ws subprotocol will receive an error when they try to send binary data frames. Before, binary data frames were silently ignored.

While vaguely defined in the protocol, the legacy graphql-ws subprotocol is generally understood to only support text data frames.

Contributed by Jonathan Ehwald via [PR #3633](strawberry-graphql/strawberry#3633)

0.241.0 - 2024-09-16

You can now configure your schemas to provide a custom subclass of strawberry.types.Info to your types and queries.

import strawberry
from strawberry.schema.config import StrawberryConfig
from .models import ProductModel
class CustomInfo(strawberry.Info):
@​property
def selected_group_id(self) -> int | None:
"""Get the ID of the group you're logged in as."""
return self.context["request"].headers.get("Group-ID")
@​strawberry.type
class Group:
id: strawberry.ID
name: str
@​strawberry.type
</tr></table>

... (truncated)

Commits

• 2f21067 Release 🍓 0.243.0
• 37265b2 Disable multipart uploads by default (#3645)
• 18f0f5d Fix missing return annotation in get_customer docs (#3642)
• ab16971 Release 🍓 0.242.0
• 63528a5 Let legacy ws clients know about invalid data frames (#3633)
• 2941146 [pre-commit.ci] pre-commit autoupdate (#3618)
• a162c9b Release 🍓 0.241.0
• 7287047 Add ability to set a custom info class for a schema (#3592)
• 13bd97b Remove old link
• 2d96d23 Release 🍓 0.240.4
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.