build: Upgrade remaining @wordpress/* packages to .38 series#324
Draft
dcalhoun wants to merge 2 commits intofix/format-library-upgradefrom
Draft
build: Upgrade remaining @wordpress/* packages to .38 series#324dcalhoun wants to merge 2 commits intofix/format-library-upgradefrom
dcalhoun wants to merge 2 commits intofix/format-library-upgradefrom
Conversation
dcalhoun
added
[Type] Build Tooling
dcalhoun
force-pushed
the
fix/format-library-upgrade
branch
from
f85d276 to
80ba09d
Compare
dcalhoun
force-pushed
the
build/upgrade-wordpress-deps-to-38
branch
from
dbb27fe to
8236350
Compare
dcalhoun
force-pushed
the
fix/format-library-upgrade
branch
from
80ba09d to
f1f6a07
Compare
dcalhoun
force-pushed
the
build/upgrade-wordpress-deps-to-38
branch
from
8236350 to
cc41f92
Compare
Upgrade all @wordpress/* dependencies to their .38.0 versions to align with @wordpress/format-library@5.38.0's requirement for @wordpress/components@^32.0.0. The previous mix of .36.0 and .38.0 packages caused duplicate @wordpress/components installations (v30.9.0 at the root and v32.0.0 nested), which led to React context mismatches and block rendering failures.
Regenerate patches for @wordpress/block-editor (15.11.0 -> 15.12.0), @wordpress/block-library (9.36.0 -> 9.39.0), @wordpress/editor (14.36.0 -> 14.39.0), and @wordpress/rich-text (7.38.0 -> 7.39.0). The underlying fixes are unchanged; only the target versions and file extensions (.js -> .mjs) were updated.
dcalhoun
force-pushed
the
build/upgrade-wordpress-deps-to-38
branch
from
cc41f92 to
2522054
Compare
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.
What?
Upgrade all remaining
@wordpress/*packages from the .36 series to the .38 series to align with@wordpress/format-library@5.38.0.Why?
After upgrading
@wordpress/format-libraryto 5.38.0 (in #323), the project had a mix of .36.0 and .38.0 packages. This caused duplicate@wordpress/componentsinstallations (v30.9.0 at the root and v32.0.0 nested under format-library), which can lead to React context mismatches and block rendering failures.Upgrading all packages to the .38 series eliminates the duplicate installations and ensures a single, consistent dependency tree.
How?
@wordpress/*dependencies inpackage.jsonto their .38.0 versions@wordpress/block-editor15.11.0 → 15.12.0@wordpress/block-library9.36.0 → 9.39.0 (.js→.mjs)@wordpress/editor14.36.0 → 14.39.0 (.js→.mjs)@wordpress/rich-text7.38.0 → 7.39.0The underlying patch fixes are unchanged; only the target versions and file extensions were updated.
Testing Instructions
npm ci— all patches should apply cleanly with no warningsAccessibility Testing Instructions
No UI changes — this is a dependency alignment upgrade.