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

Update Readme.txt tested up to 6.4 #56427

Merged
merged 2 commits into from
Nov 22, 2023
Merged

Update Readme.txt tested up to 6.4 #56427

merged 2 commits into from
Nov 22, 2023

Conversation

bph
Copy link
Contributor

@bph bph commented Nov 22, 2023

What?

Update the version in "Tested up to" section of the readme.txt of the plugin to the latest WordPress version.

Why?

To avoid the "This plugin hasn't been tested for your current version of WordPress" banner in the plugin repo and plugin workflow on WPAdmin

@bph bph added [Type] Bug An existing feature does not function as intended Gutenberg Plugin Issues or PRs related to Gutenberg Plugin management related efforts labels Nov 22, 2023
@bph bph self-assigned this Nov 22, 2023
@@ -141,7 +141,7 @@ For example, running the `start` script from inside the generated folder (`npm s

## External Project Templates

[Click here](https://developer.wordpress.org/block-editor/reference-guides/packages/packages-create-block-tutorial-template/) for information on External Project Templates
[Click here](https://developer.wordpress.org/block-editor/reference-guides/packages/packages-create-block/packages-create-block-external-template/) for information on External Project Templates
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesn't look relevant based on the PR's description, but it's a good change we can include.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A I seem to have goofed this simple thing... how do I remove that file?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious. This change was already merged in #56106, but it's not harmful to do it again

@bph bph merged commit 3b380b0 into trunk Nov 22, 2023
54 checks passed
@bph bph deleted the docs/tested-up-to branch November 22, 2023 11:20
@github-actions github-actions bot added this to the Gutenberg 17.2 milestone Nov 22, 2023
@youknowriad
Copy link
Contributor

Just noting that this PR had an impact on the performance job, it now started failing on trunk. In general when we update the "Tested up to", I think we should probably change the "base" commit used for performance jobs.

@gziolo
Copy link
Member

gziolo commented Nov 23, 2023

It looks like after 352ab99, there are the same fatal errors reported. Can you explain how a change in the readme file impacts the performance job so we could document it?

@youknowriad
Copy link
Contributor

The "Tested up to" flag is used as a "base WordPress version" for the docker containers that are used in the performance jobs. The reason is that the performance jobs compare current commit with an old commit and upon release, the compare current release with WP version - 1. So the WP version need to be one that is older than WP version - 1 but it also need to be one that is supported by the Gutenberg plugin today.

@youknowriad
Copy link
Contributor

That said, I'm not out of ideas about the current failure, we need to debug further.

@bph
Copy link
Contributor Author

bph commented Nov 23, 2023

That's super interesting to learn. Good luck troubleshooting this. 🤗

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Gutenberg Plugin Issues or PRs related to Gutenberg Plugin management related efforts [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants