Account Protection: Update breached password notice wording

[bobmatyas]

Fixes #

Proposed changes

• Update the breached password notice shown by Account Protection. It said the feature "was automatically activated with a recent Jetpack update", which stops being accurate once Account Protection: Do not activate by default on new connections #52715 stops activating Account Protection by default. It now reads: "This security feature is enabled on this site to help keep your account safe."
• Update the matching assertion in Password_Detection_Test.
• Add changelog entries for the package and for the Jetpack and Jetpack Protect plugins, since site owners of both can see this notice.

Related product discussion/links

• Follow-up to Account Protection: Do not activate by default on new connections #52715 (listed there as a known follow-up, and flagged in review).
• https://linear.app/a8c/issue/JETH-10031/jetpack-nmit-disable-auto-activation-of-account-protection-in-jetpack

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

No.

Testing instructions

Automated

• jp test php packages/account-protection

Manual

1. On a connected Jetpack (or Jetpack Protect) site running this branch, turn on Account Protection under Jetpack → Settings → Security.
2. Create a user with the Author role or higher, and give it a password that appears in known breaches (for example password123).
3. Log out, then log in as that user.
4. On the "password may appear in a known data breach" screen, confirm the second paragraph reads: "This security feature is enabled on this site to help keep your account safe."
5. Confirm the rest of the screen (verification code email, code entry) works as before.

🤖 Generated with Claude Code

[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 (Jetpack), and enable the update/account-protection-notice-wording branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/account-protection-notice-wording

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!

---

Jetpack plugin:

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

• WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly:
  • Scheduled release: October 6, 2026

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

---

Protect plugin:

No scheduled milestone found for this plugin.

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 · JS report