Closed polishq 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:
[x] 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.
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
[vtex-apps_reviews-and-ratings-ts] Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells
No Coverage information
0.0% Duplication
[vtex-apps_reviews-and-ratings-dotnet] Kudos, SonarCloud Quality Gate passed!
Your PR has been merged! App is being published. :rocket: Version 3.11.0 → 3.11.1
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.reviews-and-ratings@3.11.1
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?
App is unable to create MasterData schema in some cases, and this error has poor visibility.
This PR improves several things:
VerifySchema()
more oftenVerifySchema()
API requests (and any other requests to VBASE or MD)@context(provider: '...')
directive to all queries and mutationsHow to test it?
Linked here: https://vta--vta.myvtex.com/admin/reviews-ratings/pending/
Previously, no reviews were showing up in the admin because the MD schema had not been applied.