Closed andreaugusto closed 2 years ago
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)
[x] 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.
Warnings | |
---|---|
:warning: | :eyes: The size of this pull request seems relatively large (**>420** modifications). Consider splitting it into smaller pull requests to help make reviews easier and faster. |
Generated by :no_entry_sign: dangerJS against 34199dad6dada4226e01b19601b8b53e0483f045
Your PR has been merged! App is being published. :rocket: Version 2.149.4 → 2.150.0
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.150.0
After that your app will be updated on all accounts.
For more information on the deployment process check the docs. :book:
What problem is this solving?
This PR adds a Profile System V2 client. This new Profile System is the one that supports PII protection. The way we are using it is transparent to the end-user. There's some back and forth data translation because of it.
How to test it?
https://profilesystempii--qastoreeu.myvtex.com/_secure/account/orders#/profile To query for the data (and then know that is PII enabled), you can use the Profile System V2 API and look for your user email.
Screenshots or example usage:
There are no UI changes on this one.