Fix/newsletter welcome message html wpses

mikestottuk commented 4 days ago

Proposed changes:

Allows some additional HTML in the welcome email message.

Other information:

[ ] Have you written new tests for your changes, if applicable?
[ ] Have you checked the E2E test CI results, and verified that your changes do not break them?
[ ] Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Testing a fix

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

No

Testing instructions:

Using the following welcome message

Welcome to Jetpack CRM. The no-nonsense CRM built for entrepreneurs and small businesses. We'll send you <a href="[https://jetpackcrm.com/category/product-updates/?utm_source=welcome_email&amp;utm_medium=email&amp;utm_campaign=welcome](https://jetpackcrm.com/category/product-updates/?utm_source=welcome_email&utm_medium=email&utm_campaign=welcome)">product updates</a> as well as news and promotions from time to time. 

Here's how to get the most out of Jetpack CRM

<ul>
<li>Learn how to <a href="[https://kb.jetpackcrm.com/article-categories/getting-started/?utm_source=welcome_email&amp;utm_medium=email&amp;utm_campaign=welcome](https://kb.jetpackcrm.com/article-categories/getting-started/?utm_source=welcome_email&utm_medium=email&utm_campaign=welcome)">get started</a></li>
<li>Subscribe to our <a href="https://www.youtube.com/@jetpackcrm?sub_confirmation=1">YouTube channel</a></li>
<li>Purchase <a href="[https://jetpackcrm.com/pricing/?utm_source=welcome_email&amp;utm_medium=email&amp;utm_campaign=welcome](https://jetpackcrm.com/pricing/?utm_source=welcome_email&utm_medium=email&utm_campaign=welcome)">a bundle</a> and get the most out of your CRM</li>
</ul>

We're excited to have you on this journey. 

Mike - Jetpack CRM co-founder 
<em>Any questions - you can follow us on <a href="https://x.com/jetpackcrm">X/Twitter</a></em>

In trunk, the ul and li and em elements would be stripped. In this branch they should not be stripped.

github-actions[bot] commented 4 days ago

Thank you for your PR!

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

:white_check_mark: Include a description of your PR changes.
:white_check_mark: Add a "[Status]" label (In Progress, Needs Team Review, ...).
:white_check_mark: Add testing instructions.
:white_check_mark: Specify whether this PR includes any changes to data or privacy.
:white_check_mark: 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 :robot:

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

Follow this PR Review Process:

Ensure all required checks appearing at the bottom of this PR are passing.
Choose a review path based on your changes:
- A. Team Review: add the "[Status] Needs Team Review" label
  - For most changes, including minor cross-team impacts.
  - Example: Updating a team-specific component or a small change to a shared library.
- B. Crew Review: add the "[Status] Needs Review" label
  - For significant changes to core functionality.
  - Example: Major updates to a shared library or complex features.
- C. Both: Start with Team, then request Crew
  - For complex changes or when you need extra confidence.
  - Example: Refactor affecting multiple systems.
Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

WordPress.com Simple releases happen semi-continuously (PCYsg-Jjm-p2).
WoA releases happen weekly.
Releases to self-hosted sites happen monthly. The next release is scheduled for none scheduled (scheduled code freeze on undefined).

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

github-actions[bot] commented 4 days ago

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 WordPress.com Simple 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, and enable the fix/newsletter-welcome-message-html_wpses branch.

To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack fix/newsletter-welcome-message-html_wpses

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

Automattic / jetpack