refactor: Bump @apollo/client from 3.13.8 to 4.3.1

[dependabot]

Bumps @apollo/client from 3.13.8 to 4.3.1.

Release notes

Sourced from @​apollo/client's releases.

@​apollo/client@​4.3.1

Patch Changes

• #13464 37f700e Thanks @​jerelmiller! - Fix an issue where useLazyQuery did not rerender with new variables until the network request had completed when calling execute with new variables while a request was already in-flight.

@​apollo/client@​4.3.0

Minor Changes

• #13447 24133fe Thanks @​jerelmiller! - Field policies and inputObjects can now tell the cache whether a field is a list of scalars or a scalar whose value is an array. Previously all arrays were iterated and only the inner type was provided to the scalar parse/serialize functions.

  This required some breaking changes from previous prerelease versions:

  • The field policy scalar option and inputObjects type string now use GraphQL list syntax to mark a field as a list of scalars
  • The abstract cache.getScalarForField is now cache.getScalarTypeForField and is expected to return the string representing the scalar type rather than the Scalar instance

  new InMemoryCache({
    scalars: {
      DateTime: new Scalar(/*...*/),
    },
    inputObjects: {
      EventFilter: {
        fields: {
          // Previously only the scalar type was provided
          datesBefore: "DateTime",
      // List syntax now required
      datesAfter: "[DateTime]",
      dates2d: "[[DateTime]]",
    },
  },
  
  },
  typePolicies: {
  Event: {
  fields: {
  // Previously only the scalar type was provided
  datesBefore: {
  scalar: "DateTime",
  },
      // List syntax now required
      datesAfter: {
        scalar: "[DateTime]",
      },
      dates2d: {
        scalar: "[[DateTime]]",
      },
    },
  },
  
  },

... (truncated)

Changelog

Sourced from @​apollo/client's changelog.

4.3.1

Patch Changes

• #13464 37f700e Thanks @​jerelmiller! - Fix an issue where useLazyQuery did not rerender with new variables until the network request had completed when calling execute with new variables while a request was already in-flight.

4.3.0

Minor Changes

• #13447 24133fe Thanks @​jerelmiller! - Field policies and inputObjects can now tell the cache whether a field is a list of scalars or a scalar whose value is an array. Previously all arrays were iterated and only the inner type was provided to the scalar parse/serialize functions.

  This required some breaking changes from previous prerelease versions:

  • The field policy scalar option and inputObjects type string now use GraphQL list syntax to mark a field as a list of scalars
  • The abstract cache.getScalarForField is now cache.getScalarTypeForField and is expected to return the string representing the scalar type rather than the Scalar instance

  new InMemoryCache({
    scalars: {
      DateTime: new Scalar(/*...*/),
    },
    inputObjects: {
      EventFilter: {
        fields: {
          // Previously only the scalar type was provided
          datesBefore: "DateTime",
      // List syntax now required
      datesAfter: "[DateTime]",
      dates2d: "[[DateTime]]",
    },
  },
  
  },
  typePolicies: {
  Event: {
  fields: {
  // Previously only the scalar type was provided
  datesBefore: {
  scalar: "DateTime",
  },
      // List syntax now required
      datesAfter: {
        scalar: "[DateTime]",
      },
      dates2d: {
        scalar: "[[DateTime]]",
      },
    },

... (truncated)

Commits

• 4bb0b7a Version Packages (#13465)
• 37f700e Force rerender useLazyQuery when variables change while request is in-fligh...
• d4f8770 Version Packages (#13461)
• d3c455f Exit prerelease mode (#13460)
• 0c925a4 Release 4.3 (#13243)
• 4060465 Merge branch 'main' into release-4.3
• 9cd4118 Add custom scalars documentation (#13439)
• 766a86e Add documentation for the TypeScript changes in 4.3 (#13436)
• f342046 Version Packages (rc) (#13450)
• f1244b1 Fix release workflow (#13449)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​apollo/client since your current version.

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 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)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 1758efe4-70e8-4763-a43b-04f56c0a54b9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}