vtex-apps / availability-notify

3 stars 3 forks source link

[NOTIFIER-56] Fix/process unset notifications test #70

Closed Arturo777 closed 2 years ago

Arturo777 commented 2 years ago

What was made in this PR?

The mutation ProcessUnsentRequest didn't have it's own type graphql in the dotnet folder, and neither in the main graphql schema.

Worskpace to test

vtex-io-ci-cd[bot] commented 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:

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

sonarcloud[bot] commented 2 years ago

[vtex-apps_availability-notify-dotnet] Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 1 Code Smell

0.0% 0.0% Coverage
0.0% 0.0% Duplication

sonarcloud[bot] commented 2 years ago

[vtex-apps_availability-notify-ts] Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

vtex-io-ci-cd[bot] commented 2 years ago

Your PR has been merged! App is being published. :rocket: Version 1.8.4 → 1.8.5

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.availability-notify@1.8.5

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. :book: