You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I updated to the latest version 30.8.0 according to the changelog. My build started failing locally due to some missing packages which after investigation, I saw were dependencies of wp-scripts. I was digging into how they were not installed with npm install and noticed a version discrepancy. npmjs lists 30.8.1 as the latest, but the docs on GitHub list 30.8.0.
I updated it to 30.8.1 and my build worked again. I'm unsure if 30.8.0 is broken for anyone else, but this issue is simply about the discrepancy between the changelog and the published version. I don't know the differences between these two releases, but we do have this: @wordpress/[email protected]...@wordpress/[email protected] and I assume this #68467 is related.
The easy fix is to update the changelog file to include the latest version and list relevant changes. I don't know what steps are required to update the changelog(s) but I expect there is some command to generate based on commits/PRs so I won't submit a PR to update that file (yet).
Note: I haven't checked if other packages are having similar issues, and I am not sure why 30.8.0 build didn't work but 30.8.1 did.
Description
I have a project using wp-scripts for builds.
I updated to the latest version
30.8.0
according to the changelog. My build started failing locally due to some missing packages which after investigation, I saw were dependencies of wp-scripts. I was digging into how they were not installed withnpm install
and noticed a version discrepancy. npmjs lists30.8.1
as the latest, but the docs on GitHub list30.8.0
.I updated it to
30.8.1
and my build worked again. I'm unsure if30.8.0
is broken for anyone else, but this issue is simply about the discrepancy between the changelog and the published version. I don't know the differences between these two releases, but we do have this: @wordpress/[email protected]...@wordpress/[email protected] and I assume this #68467 is related.The easy fix is to update the changelog file to include the latest version and list relevant changes. I don't know what steps are required to update the changelog(s) but I expect there is some command to generate based on commits/PRs so I won't submit a PR to update that file (yet).
Note: I haven't checked if other packages are having similar issues, and I am not sure why
30.8.0
build didn't work but30.8.1
did.Step-by-step reproduction instructions
Screenshots, screen recording, code snippet
No response
Environment info
No response
Please confirm that you have searched existing issues in the repo.
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Please confirm which theme type you used for testing.
The text was updated successfully, but these errors were encountered: