Plugin Blueprints: Can set WP / PHP version to old values which results in preview failing to load

[dd32]

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 ​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)