Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Init Protect 1.3.1-a #28576

Merged
merged 4 commits into from
Jan 25, 2023
Merged

Init Protect 1.3.1-a #28576

merged 4 commits into from
Jan 25, 2023

Conversation

nateweller
Copy link
Contributor

Proposed changes:

  • Init Jetpack Protect 1.3.1-a cycle.

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

N/A

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

No

Testing instructions:

  • Proof-read

@nateweller nateweller added [Status] Needs Review To request a review from fellow Jetpack developers. Label will be renamed soon. [Plugin] Protect A plugin with features to protect a site: brute force protection, security scanning, and a WAF. labels Jan 25, 2023
@nateweller nateweller self-assigned this Jan 25, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Jan 25, 2023

Are you an Automattician? You can now test your Pull Request on WordPress.com. On your sandbox, run bin/jetpack-downloader test jetpack prerelease to get started. More details: p9dueE-5Nn-p2

@github-actions github-actions bot added the RNA label Jan 25, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Jan 25, 2023

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.
  • ✅ All commits were linted before commit.
  • ✅ Add a "[Status]" label (In Progress, Needs Team 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 🤖


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 (other than "Required review") 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 you’ve done so, switch to the "[Status] Needs Review" label; someone from Jetpack Crew will then review this PR and merge it to be included in the next Jetpack release.


Protect plugin:

  • Next scheduled release: February 7, 2023.
  • Scheduled code freeze: January 30, 2023.

samiff
samiff previously approved these changes Jan 25, 2023
@samiff samiff added [Status] Ready to Merge Go ahead, you can push that green button! and removed [Status] Needs Review To request a review from fellow Jetpack developers. Label will be renamed soon. labels Jan 25, 2023
@nateweller nateweller enabled auto-merge (squash) January 25, 2023 23:04
@nateweller nateweller merged commit 5f73e7d into trunk Jan 25, 2023
@nateweller nateweller deleted the prerelease branch January 25, 2023 23:42
@github-actions github-actions bot added this to the protect/1.3.0 milestone Jan 25, 2023
@github-actions github-actions bot removed the [Status] Ready to Merge Go ahead, you can push that green button! label Jan 25, 2023
n3f pushed a commit that referenced this pull request Jan 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment