Description
Every default Playground boot logs a version-mismatch warning that is not a real mismatch:
Loaded WordPress version (7.0) differs from requested version (latest).
The website defaults the wp version to the literal string latest resolve-blueprint-from-url.ts:223. That alias is stored in requestedWordPressVersion as-is, but the comparison in finalizeAfterBoot() runs against the resolved build version returned by getLoadedWordPressVersion():
https://github.com/WordPress/wordpress-playground/blob/trunk/packages/playground/remote/src/lib/playground-worker-endpoint.ts#L365-L370
'latest' !== '7.0', so the warning fires even though the correct build loaded.
nightly is already normalized to trunk at the assignment site, and beta/trunk are real keys in wp-versions.json, so latest is the only alias that mis-compares — and it happens to be the default, so this fires for essentially every visitor.
Impact is low (a console warning, not shown in the Logs pane), but it is noise on every page load and it undermines the check: a genuine mismatch — the case the warning exists to catch, per the comment about WP loaded from browser storage — is indistinguishable from the default-boot false positive.
Step-by-step reproduction instructions
- Open https://playground.wordpress.net/ (or
npm run dev) with the browser console open.
- Wait for WordPress to finish booting.
- Observe the warning above.
- For contrast, load
?wp=6.9 — an explicit version produces no warning.
Expected behavior
No warning when the loaded build is the one the requested alias resolves to. The warning should still fire for a genuine mismatch.
Description
Every default Playground boot logs a version-mismatch warning that is not a real mismatch:
The website defaults the
wpversion to the literal stringlatestresolve-blueprint-from-url.ts:223. That alias is stored inrequestedWordPressVersionas-is, but the comparison infinalizeAfterBoot()runs against the resolved build version returned bygetLoadedWordPressVersion():https://github.com/WordPress/wordpress-playground/blob/trunk/packages/playground/remote/src/lib/playground-worker-endpoint.ts#L365-L370
'latest' !== '7.0', so the warning fires even though the correct build loaded.nightlyis already normalized totrunkat the assignment site, andbeta/trunkare real keys inwp-versions.json, solatestis the only alias that mis-compares — and it happens to be the default, so this fires for essentially every visitor.Impact is low (a console warning, not shown in the Logs pane), but it is noise on every page load and it undermines the check: a genuine mismatch — the case the warning exists to catch, per the comment about WP loaded from browser storage — is indistinguishable from the default-boot false positive.
Step-by-step reproduction instructions
npm run dev) with the browser console open.?wp=6.9— an explicit version produces no warning.Expected behavior
No warning when the loaded build is the one the requested alias resolves to. The warning should still fire for a genuine mismatch.