Prior `variables` are being merged into subsequent queries

Intended outcome: In version 3.5.10 if you executed the same query on a subsequent render with different variables, it’d only use those variables. For example:

• On first render, you do useQuery(query, { variables: { first: 10 } })
• On second render, if you do useQuery(query, { variables: { last: 10 } }), you’d expect the query to only execute with the variables { last: 10 }.

Actual outcome: In version 3.6.0 if you execute the same query on a subsequent render with different variables, it’ll merge the previously used variables. For example:

• On first render, you do useQuery(query, { variables: { first: 10 } })
• On second render, if you do useQuery(query, { variables: { last: 10 } }), the variables that actually get used in the query are { first: 10, last: 10 }.

How to reproduce the issue: To reproduce the issue, please reference this repo. There’s fairly simple steps to reproduce the issue in the README.

Please let me know if I should provide any additional details, from a quick preliminary investigation, I believe the issue may have been introduced in this PR, but I could be wrong.

Versions @apollo-client: 3.6.0

[benjamn]

@AkiraJ48 My proposed fix #9741 can be tested now by running npm i @apollo/client@beta to get version 3.7.0-alpha.6. Please let us know if that version seems to help (over in #9671). Thanks!

Note: while that version says 3.7, PR #9741 is targeting the main branch, implying a 3.6.x patch release (not 3.7).

[72636c]

3.6.5 is looking good for us, thanks for the quick fix!