chore(deps): bump @apollo/client from 3.11.10 to 3.12.5

[dependabot]

Bumps @apollo/client from 3.11.10 to 3.12.5.

Release notes

Sourced from @​apollo/client's releases.

v3.12.5

Patch Changes

• #12252 cb9cd4e Thanks @​jerelmiller! - Changes the default behavior of the MaybeMasked type to preserve types unless otherwise specified. This change makes it easier to upgrade from older versions of the client where types could have unexpectedly changed in the application due to the default of trying to unwrap types into unmasked types. This change also fixes the compilation performance regression experienced when simply upgrading the client since types are now preserved by default.

  A new mode option has now been introduced to allow for the old behavior. See the next section on migrating if you wish to maintain the old default behavior after upgrading to this version.

  Migrating from <= v3.12.4

  If you've adopted data masking and have opted in to using masked types by setting the enabled property to true, you can remove this configuration entirely:

  -declare module "@apollo/client" {
  -  interface DataMasking {
  -    mode: "unmask"
  -  }
  -}

  If you prefer to specify the behavior explicitly, change the property from enabled: true, to mode: "preserveTypes":

  declare module "@apollo/client" {
    interface DataMasking {
  -    enabled: true
  +    mode: "preserveTypes"
    }
  }

  If you rely on the default behavior in 3.12.4 or below and would like to continue to use unmasked types by default, set the mode to unmask:

  declare module "@apollo/client" {
    interface DataMasking {
      mode: "unmask";
    }
  }

v3.12.4

Patch Changes

• #12236 4334d30 Thanks @​charpeni! - Fix an issue with refetchQueries where comparing DocumentNodes internally by references could lead to an unknown query, even though the DocumentNode was indeed an active query—with a different reference.

v3.12.3

Patch Changes

• #12214 8bfee88 Thanks @​phryneas! - Data masking: prevent infinite recursion of ContainsFragmentsRefs type

... (truncated)

Changelog

Sourced from @​apollo/client's changelog.

3.12.5

Patch Changes

• #12252 cb9cd4e Thanks @​jerelmiller! - Changes the default behavior of the MaybeMasked type to preserve types unless otherwise specified. This change makes it easier to upgrade from older versions of the client where types could have unexpectedly changed in the application due to the default of trying to unwrap types into unmasked types. This change also fixes the compilation performance regression experienced when simply upgrading the client since types are now preserved by default.

  A new mode option has now been introduced to allow for the old behavior. See the next section on migrating if you wish to maintain the old default behavior after upgrading to this version.

  Migrating from <= v3.12.4

  If you've adopted data masking and have opted in to using masked types by setting the enabled property to true, you can remove this configuration entirely:

  -declare module "@apollo/client" {
  -  interface DataMasking {
  -    mode: "unmask"
  -  }
  -}

  If you prefer to specify the behavior explicitly, change the property from enabled: true, to mode: "preserveTypes":

  declare module "@apollo/client" {
    interface DataMasking {
  -    enabled: true
  +    mode: "preserveTypes"
    }
  }

  If you rely on the default behavior in 3.12.4 or below and would like to continue to use unmasked types by default, set the mode to unmask:

  declare module "@apollo/client" {
    interface DataMasking {
      mode: "unmask";
    }
  }

3.12.4

Patch Changes

• #12236 4334d30 Thanks @​charpeni! - Fix an issue with refetchQueries where comparing DocumentNodes internally by references could lead to an unknown query, even though the DocumentNode was indeed an active query—with a different reference.

3.12.3

Patch Changes

... (truncated)

Commits

• acf52e9 Version Packages (#12259)
• cb9cd4e Unmask types with explicit mode: "unmask" and default to leave the type alo...
• dd3d653 Update maintainers
• 6109951 Update ROADMAP.md
• 2944f70 chore(deps): update cimg/node docker tag to v23.5.0 (#12225)
• 4b410d3 fix timing problems in tests introduced by latest React canary (#12234)
• 0a0298f improved import migration (#12244)
• 6dcb6ba docs: add meta descriptions to top-level pages (#12239)
• db6a442 Version Packages (#12237)
• d3b4827 Merge pull request #12238 from apollographql/ms/update-discord-to-discourse
• 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 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)