[Blueprints] Resolve preferred Blueprint v2 WordPress versions - #3894
Merged
Conversation
adamziel
force-pushed
the
resolve-v2-runtime-constants
branch
from
July 3, 2026 13:14
2a1136d to
097c970
Compare
adamziel
force-pushed
the
resolve-v2-runtime-wordpress-preferred
branch
from
July 3, 2026 13:15
3ab6bb1 to
97b7435
Compare
adamziel
force-pushed
the
resolve-v2-runtime-constants
branch
from
July 3, 2026 13:21
097c970 to
083e186
Compare
adamziel
force-pushed
the
resolve-v2-runtime-wordpress-preferred
branch
from
July 3, 2026 13:21
97b7435 to
c5ae5aa
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
Uses
wordpressVersion.preferredfrom Blueprint v2 constraint objects when resolving runtime configuration. Constraints without a preferred version keep the currentlatestfallback.Why
This is a small step toward honoring Blueprint v2 version constraints without adding full constraint solving yet. It lets consumers that already provide an explicit preferred WordPress version get the matching runtime instead of silently booting
latest.Testing
npm run format:uncommittednpm exec nx run playground-blueprints:test:vite -- --testFiles=packages/playground/blueprints/src/tests/v2/resolve-runtime-configuration.spec.tsnpm exec nx run playground-blueprints:typechecknpm exec nx run playground-blueprints:lintgit diff --checkPart of #2592.