Closed gabiruuuuu closed 1 month 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.
Beep boop :robot:
I noticed you didn't make any changes at the docs/
folder
In order to keep track, I'll create an issue if you decide now is not a good time
Your PR has been merged! App is being published. :rocket: Version 2.171.2 → 2.172.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.172.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?
Delivery Promises is a key initiative led by the Order Allocation team in partnership with Intelligent Search, its main goal is to provide a unified system to resolve product availability and use it on Search and Navigation to greatly reduce broken carts because of availability differences on Checkout.
To this end, we need to make changes to how IS uses simulation to fetch Hot prices and stock to start using the postalCode argument.
How to test it?
The changes are optional in the schema and should only affect stores that use the DP feature and will call simulation with the postal code, which at the moment is just one T3 account on closed beta.
Here is an example of an workspace with the updated versions of this app and IS API, for a store that doesn't use DP, to validate that everything still works as intended.
Workspace
Screenshots or example usage:
Describe alternatives you've considered, if any.
Related to / Depends on
How does this PR make you feel? :link:
![](put .gif link here - can be found under "advanced" on giphy)