[wp-meta] [Making WordPress.org] #7812: Plugin Blueprints: Can set WP / PHP version to old values which results in preview failing to load

[Making WordPress.org]

#7812: Plugin Blueprints: Can set WP / PHP version to old values which results in
preview failing to load
------------------------------+--------------------
 Reporter:  dd32              |      Owner:  (none)
     Type:  defect (bug)      |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 The plugin preview blueprints can define the PHP Version and WP version.

 This can cause problems when a plugin requires other plugins, which update
 their requirements at a later date.

 Ideally, IMHO, blueprints should always load the latest version of
 WordPress. This shouldn't be an option that the developer has to set, nor
 that they can override. We want plugins to be previewed using what users
 are using, the latest version.


 For example, I've just come across a plugin which defines this: (via
 [https://wordpress.slack.com/archives/C06Q5DCKZ3L/p1730097268759009 a
 playground error log in slack])
 {{{
   "preferredVersions": {
     "php": "7.4",
     "wp": "6.4"
   },
 }}}

 The plugin requires WooCommerce, which now requires WP 6.5 at a minimum,
 and so this other plugins preview now fails to load.

 So, to round up:
  - `preferredVersions.wp` should be forced to `latest` in all cases.
  - `preferredVersions.php` should ideally be `min( preferredVersions.php,
 $plugin_requires_php )` if something is set (otherwise fallback to
 whatever playground defaults to on the day)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7812>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org