-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add WP version comparison script #68
base: main
Are you sure you want to change the base?
Conversation
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 @swissspidy, this looks great overall! A few minor comments. I wasn't able to complete the process locally due to an error.
"homepage": "https://github.com/swissspidy/compare-wp-performance#readme", | ||
"type": "module", | ||
"devDependencies": { | ||
"@wordpress/env": "^8.4.0", |
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.
Couldn't we alternatively use an older version that doesn't have the bug and thus doesn't require the patch and extra package.json
workaround?
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 will need to check what‘s possible / where the bug was introduced and if there are features we can live without or not.
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.
The bug has since been resolved, so we can use a newer version without a patch, but it still requires 2 package.json files. Or we leverage a global install.
@swissspidy I realize this somehow fell off the radar, but was wondering whether we could pick it up again. I think it's close, could you follow up on #68 (comment) and see whether there are any new changes in your repo that should be ported into this PR when you get a chance? |
Yeah I'll need to revisit this and merge in the latest changes. But holding off a bit now because it's not urgent (for 6.4 we can still use the existing repo) and there might be significant changes needed when tackling all the variance issues. |
Ports over the GitHub action and the manual Bash script from https://github.com/swissspidy/compare-wp-performance
The individual
package.json
files are unfortunately necessary right now because of WordPress/gutenberg#51419