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

Add an integration to check the Requires Yoast SEO header. #21391

Draft
wants to merge 2 commits into
base: trunk
Choose a base branch
from

Conversation

enricobattocchi
Copy link
Member

Context

Summary

This PR can be summarized in the following changelog entry:

  • Prevents the installation of addons requiring a higher Yoast SEO version than the current one.

Relevant technical choices:

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

Relevant test scenarios

  • Changes should be tested with the browser console open
  • Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
  • Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
  • Changes should be tested on different browsers
  • Changes should be tested on multisite

Test instructions for QA when the code is in the RC

  • QA should use the same steps as above.

QA can test this PR by following these steps:

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

UI changes

  • This PR changes the UI in the plugin. I have added the 'UI change' label to this PR.

Other environments

  • This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.

Documentation

  • I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

  • I have tested this code to the best of my abilities.
  • During testing, I had activated all plugins that Yoast SEO provides integrations for.
  • I have added unit tests to verify the code works as intended.
  • If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
  • I have written this PR in accordance with my team's definition of done.
  • I have checked that the base branch is correctly set.

Innovation

  • No innovation project is applicable for this PR.
  • This PR falls under an innovation project. I have attached the innovation label.
  • I have added my hours to the WBSO document.

Fixes #

@enricobattocchi enricobattocchi added the changelog: enhancement Needs to be included in the 'Enhancements' category in the changelog label May 17, 2024
@coveralls
Copy link

coveralls commented May 17, 2024

Pull Request Test Coverage Report for Build e4e0597cc1e5bb72b9559ffa29b07f5e3b144e93

Details

  • 0 of 47 (0.0%) changed or added relevant lines in 1 file are covered.
  • 592 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.04%) to 52.565%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/integrations/admin/check-required-version.php 0 47 0.0%
Files with Coverage Reduction New Missed Lines %
src/generated/container.php 592 0.0%
Totals Coverage Status
Change from base Build af78a54b018b51ef33b2a20dd24d759b1c3fd3e8: -0.04%
Covered Lines: 28300
Relevant Lines: 54459

💛 - Coveralls

@enricobattocchi enricobattocchi force-pushed the feature/check-min-required-free-version branch from d5dfc08 to 4db4f15 Compare May 28, 2024 09:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog: enhancement Needs to be included in the 'Enhancements' category in the changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants