fix: use PATCH instead of PUT when updating clientPreferences (Profile System V2)

[iago1501]

Problem

When a user updates their newsletter preferences (updatePersonalPreferences), store-graphql was calling PUT /purchase-info sending only the clientPreferences payload. Because PUT replaces the entire entity, the paymentData field (saved cards) was being wiped from the user's profile.

This was identified as the root cause of a production incident where transactions were being cancelled via the WorldpayVTEX connector: the gatewayCallback validation was failing because the saved card appeared to belong to a "loaded profile" (no login), since the card data had been removed from the real profile after the PUT.

The Storage team blocked external write access to purchase-info as a mitigation, and this PR addresses the same issue at the store-graphql level.

Fix

Changed this.put → this.patch in updatePersonalPreferences (profileV2.ts:133).

PATCH performs a partial update, merging only clientPreferences into the existing document and leaving paymentData intact.

No other calls to purchase-info in this codebase use PUT — the V1 client uses POST /personalPreferences/ (a different endpoint) and is not affected.

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

[vtex-io-docs-bot]

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

• There's nothing new to document 🤔
• I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

• I just updated 🎉🎉

[wisneycardeal]

That change was aligned during the #inc-5621.
This point is encapsulated in a method that maintains the same signature.
So LGTM.

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 2.177.2 → 2.177.3

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy vtex.store-graphql@2.177.3

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖