docs: update the tested up WordPress version to 6.6

[MaferMazu]

Description

This updated the tested-up WordPress version to 6.6

Additional information

This version needs to be updated. Related #72

https://wordpress.org/documentation/article/wordpress-versions/

[openedx-webhooks]

Thanks for the pull request, @MaferMazu!

What's next?

Please work through the following steps to get your changes ready for engineering review:

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @mafermazu. Tag them in a comment and let them know that your changes are ready for review.

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[felipemontoya]

The change its just the line, but did you run the code in the staging env? I'm not expecting anything to fail. Just checking as it was not mentioned in the cover letter.

I checked the env and it has 6.6.1 but I don't think we need to put the minor in the file

[felipemontoya]

I leave the approval in advanced

[MaferMazu]

Sorry, I didn't mention it. Yes, I tested it with this zip file: openedx-commerce.zip (has all the recent changes).

About the major and minor, the doc says this:

Tested up to – The version of WordPress that the plugin has been tested against. This field ignores minor versions, as plugins shouldn't break with a minor update. This means a plugin only needs to define the major version it is tested against, and the WordPress.org plugin directory will automatically add the minor version. This should be numbers only, so '4.9' and not 'WP 4.9'

More about the readme header: https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/#readme-header-information

This PR is mostly doc, but it is a very important doc. We need to stay updated to avoid this #72

Updated:
I will change the chore commit message to docs because it is important, but still docs.

[openedx-webhooks]

@MaferMazu 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.