-
Notifications
You must be signed in to change notification settings - Fork 4.7k
update "requires at least" value to 5.6 #29646
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
Conversation
ntsekouras
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's 5.6 now :) - #29701
|
I think it should be 5.6 now after @youknowriad merged #29701 😄 |
gutenberg.php
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think we can remove this entirely from here? I mean we already have this value defined in readme.txt isn't that enough?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should keep them. See https://core.trac.wordpress.org/ticket/46938
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could add Tested up to here too, fwiw
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See the last comment from @SergeyBiryukov:
If the headers are defined in both readme.txt and the main plugin file, precedence is given to the plugin file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think we can remove this entirely from here? I mean we already have this value defined in readme.txt isn't that enough?
Just noting that WordPress 5.8 aims to remove parsing readme.txt files from validate_plugin_requirements(), see https://core.trac.wordpress.org/ticket/48520. Per discussion with Otto, apparently that file should only have been used for the Plugin Directory and not for core, which should retrieve the data it needs from the main plugin file instead.
So I would suggest removing the Requires at least and Requires PHP headers from the readme.txt file, and keeping them only in the main plugin file. The Plugin Directory supports that too, see https://meta.trac.wordpress.org/ticket/4514.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for clarifying. I will make sure we update @wordpress/create-block and its templates to follow the same approach.
|
Wasn't fast enough 🤣😂 @youknowriad took care of it. 👍🦄Thanks for all the comments. |
|
@bph we actually stiil need to do that if you want to give it a try. I wasn't aware of the flags in the php file personally #29646 (comment) |
|
Oh, sorry. Yes, I can update to 5.6. Hang-on |
|
@bph can you also remove the two headers from the readme.txt to avoid duplication? |
|
Updated @youknowriad - |
|
Looks like this PR needs a rebase now (conflict with the readme update on trunk). So you can do something like |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be fixed now @youknowriad -- it still shows a conflict?
|
@bph I can take care of it. |
|
Looks we have some issues with wp-env at the moment, I'll merge this after we solve these. |
of plugin file.
Description
For plugin, the minimum requirement is 5.5 - it's already updated in the readme.txt but not in the plugin header of gutenberg.php
Checklist: