-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
wp-env with "core: null" installs WP 5.4.2, not the latest version (5.6.0) #27763
Comments
@leoloso When I tested it used whatever version of WordPress I had installed previously. For me that was 5.6, I'm guessing you had 5.4.2 installed previously using wp-env? I'll label as a bug though this could probably be handled as a documentation update. |
I possibly did have WP 5.4.2, tbh I don't know. However, I also created a new folder and run If the history doesn't belong to the project but to Btw, I also set-up the config below: {
"core": "WordPress/WordPress#5.6.0"
} But it fails, with this error:
(Is this an unrelated bug? Should I create another issue?) |
It uses git refs after the hash, so for a tag this works (this is actually how I have mine set up):
The list of tags is here: |
Ok, thanks. I think the documentation could be improved then, since it doesn't mention anything about tags. I got it wrong by following the example here: {
"core": "WordPress/WordPress#5.2.0",
"plugins": [ "WordPress/wp-lazy-loading", "WordPress/classic-editor" ],
"themes": [ "WordPress/theme-experiments" ]
} |
Good catch! |
Also this:
Can this be done? Is it a documentation issue? Or there's no way currently to say "use the latest WP" and I need to explicitly use the latest tag? |
If it's not a documentation feature but instead a lacking feature, it could be implemented by fetching the version information from Note the |
|
Yeah, @noisysocks is spot on. They seem to update that image fairly quickly. In this case, it was updated to 5.6 the day of the release (december 8). So then the question is: why were you still getting an out of date image after that point? I think this would be because Docker is using a cached version of the image on your system. (That's my best guess anyways.) If you run I think our action items here are to update the documentation about this behavior, and to fix the example with the git tag |
I just tried this, both on an existing installation, and on a new one. It didn't solve the issue: It still installs WP 5.4.2. Just in case it helps, this is the output in the terminal:
|
I am not able to reproduce this problem. It's over two years old so it may have been fixed. Is there still a documentation issue outstanding? I'm going to close this, given the lack of activity over the last couple of years, but feel free to let me know if you feel it's still relevant and I'll re-open it. |
The wp-env behavior has definitely been updated so that the latest version is pulled more quickly, which matches the documented behavior. (So I removed the documentation label) |
Describe the bug
When installing
wp-env
with"core: null"
, the latest version of WordPress should be installed.However that is not happening: WordPress 5.4.2 is being installed instead.
To reproduce
Steps to reproduce the behavior:
wp-env.json
file:wp-env start
Expected behavior
The latest version of WordPress should be installed (currently 5.6.0)
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: