Automattic
My Jetpack: Test standalone update
DO NOT MERGE
Proposed changes:
This PR is just a test to produce a build including latest My Jetpack updates on a standalone plugin
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
p1709649221268149-slack-C054LN8RNVA
Does this pull request change what data or activity we track or use?
No
Testing instructions:
Instance a JN and verify My Jetpack changes on AI interstitial
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.
Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped. Then, add the "[Status] Needs Team Review" label and ask someone from your team review the code. Once reviewed, it can then be merged. If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.
Jetpack plugin:
The Jetpack plugin has different release cadences depending on the platform:
- WordPress.com Simple releases happen daily.
- WoA releases happen weekly.
- Releases to self-hosted sites happen monthly. The next release is scheduled for April 2, 2024 (scheduled code freeze on April 1, 2024).
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.
Backup plugin:
- Next scheduled release: April 2, 2024.
- Scheduled code freeze: March 25, 2024.
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.
Boost plugin:
- Next scheduled release: April 2, 2024.
- Scheduled code freeze: March 25, 2024.
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.
Search plugin:
- Next scheduled release: April 2, 2024.
- Scheduled code freeze: March 25, 2024.
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.
Social plugin:
- Next scheduled release: April 2, 2024.
- Scheduled code freeze: March 25, 2024.
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.
Starter Plugin plugin:
- Next scheduled release: April 2, 2024.
- Scheduled code freeze: March 25, 2024.
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.
Protect plugin:
- Next scheduled release: April 2, 2024.
- Scheduled code freeze: March 25, 2024.
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.
Videopress plugin:
- Next scheduled release: April 2, 2024.
- Scheduled code freeze: March 25, 2024.
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.
Migration plugin:
- Next scheduled release: April 2, 2024.
- Scheduled code freeze: March 25, 2024.
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Are you an Automattician? The PR will need to be tested on WordPress.com. This comment will be updated with testing instructions as soon the build is complete.
This PR has been marked as stale. This happened because:
- It has been inactive for the past 3 months.
- It hasn’t been labeled `[Pri] BLOCKER`, `[Pri] High`, etc.
If this PR is still useful, please do a [trunk merge or rebase](https://github.com/Automattic/jetpack/blob/trunk/docs/git-workflow.md#keeping-your-branch-up-to-date) and otherwise make sure it's up to date and has clear testing instructions. You may also want to ping possible reviewers in case they've forgotten about it. Please close this PR if you think it's not valid anymore — if you do, please add a brief explanation.
If the PR is not updated (or at least commented on) in another month, it will be automatically closed.
This PR has been automatically closed as it has not been updated in some time. If you want to resume work on the PR, feel free to restore the branch and reopen the PR.