wpcomsh: sync BLAZE_CREDITS_VOUCHER gating with WordPress.com

[jjolmo]

Proposed changes

• Sync projects/plugins/wpcomsh/wpcom-features/class-wpcom-features.php with the WordPress.com copy: BLAZE_CREDITS_VOUCHER no longer requires the gating-business-q1 sticker and now includes the monthly Business and Ecommerce bundles, so the feature map matches every eligible plan term (monthly, 1y, 2y, 3y).

Related product discussion/links

• Internal reference: DOTCOM-17871. Companion to the WordPress.com-side change (230012 on the internal wpcom repo) — this keeps the shared wpcom-features file from drifting, as flagged by the sync check there.

Does this pull request change what data or activity we track or use?

No.

Testing instructions

• No functional consumer of BLAZE_CREDITS_VOUCHER exists in wpcomsh today, so this is a mirror-consistency change: verify the BLAZE_CREDITS_VOUCHER entry in wpcom-features/class-wpcom-features.php matches the WordPress.com copy after its companion change (no sticker requirement, monthly bundles included).
• php -l projects/plugins/wpcomsh/wpcom-features/class-wpcom-features.php passes.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (WordPress.com Site Helper), and enable the update/wpcomsh-blaze-credits-voucher-all-terms branch.

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

---

Wpcomsh plugin:

• Next scheduled release: Atomic deploys happen twice daily on weekdays (p9o2xV-2EN-p2)

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report