WP-stateless latest release mentions a vulnerability fix. Although there is no active vulnerability for the version we use (2.3.3), it's probably prudent to update anyway.

Last time we tried to upgrade to 3.1.x it broke the importer (see PLANET-5899). From reports we know that this version also broke the native WP importer. But 3.2.0 also fixes compatibility issues with Wordpress, so this may be fixed (it may be the reason it was pulled from WP registry).

Tasks

• Test 3.2.0 to make sure both core and campaigns importer work.
• Since the plugin is still missing from WP registry, update the plugin definition in base.

Resources

• 3.2.0 in our GCP bucket