Fix Blueprint Version Warning Comparison

[sejas]

Related issues

• Fixes STU-1265

Proposed Changes

• Respect the Blueprint preferred versions and prefill the dropdowns
• Display warning when the version in the selected version doesn't match Blueprint
  • This state could happen when the WP version is not in the supported versions
  • Or when the user changes the selected version manually
• Update warning text from "default is" to "selected is" for clarity
• Remove unnecessary originalDefaultVersions prop

Testing Instructions

• Run npm start

Test 1: Warning appears when blueprint version uses unsupported WP version

blueprint-unsupported-wp.json

1. Click "Add site"
2. Select "Start with a Blueprint"
3. Choose a blueprint that specifies preferredVersions (e.g., WP 5.8.1)
4. Observe the warning appears even if the advanced options are collapsed
5. Open the advance settings observe the whole warning

Test 2: Warning updates dynamically when user changes dropdown

test-multiple-warnings-blueprint.json

1. Create a site with valid preferred Blueprint versions
2. Observe no warning appears
3. Change the PHP or WP version dropdown inside the advance settings
4. Observe the warning appears

Test 3: No supported PHP version

blueprint-unsupported-php.json

We didn't modify the logic, but I observed that if the PHP version is not supported, the flow displays an error validating the Blueprint in the previous step.

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[wpmobilebot]

📊 Performance Test Results

Comparing f147d0c vs trunk

site-editor

Metric	trunk	f147d0c	Diff	Change
load	2838.00 ms	2828.00 ms	-10.00 ms	🟢 -0.4%

site-startup

Metric	trunk	f147d0c	Diff	Change
siteCreation	7124.00 ms	7084.00 ms	-40.00 ms	🟢 -0.6%
siteStartup	3927.00 ms	3930.00 ms	+3.00 ms	🔴 0.1%

---

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change

[epeicher]

Thanks @sejas! This works as expected. I can see validation warnings when using versions different from those specified in the Blueprint. The WordPress version is automatically updated to latest when it is unsupported, while the unsupported php version is just discarded.

Also the warnings are displayed as soon as the versions of PHP or WordPress is changed to a different one than selected in the Blueprint. LGTM!

Incorrect WP version collapsed	Incorrect WP version expanded	Selecting different version than the Blueprint	Non-supported PHP version

[ivan-ottinger]

Thank you for the fix, Antonio! The changes work nicely!

CleanShot.2026-01-29.at.09.58.22.mp4