Remove WP 6.2 minified build after WP 6.6 release - #1632
Merged
Conversation
brandonpayton
added
[Type] Bug
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation for the change, related issues
This PR removes support for WP 6.2 which is unsupported following the WP 6.6 release.
The actual motivation for this change is to try to work around the npm package release error encountered here:
https://github.com/WordPress/wordpress-playground/actions/runs/9960370683/job/27519444281
With this change the
@wp-playground/wordpress-buildsunpacked size goes from 529M to 485M (based onduutility output for a local build). Lerna reported that the previous, successful release of the package had a size of 363.5 MB.Related to #1630
Testing Instructions (or ideally a Blueprint)
npm run devto confirm that WP 6.2 is no longer offered as an option in the UI and that Playground continues to load without error.