PLUSPOL interactive GbR

We experience the same issue and dug into the code. The error seems to come from this file: https://github.com/wp-media/wp-rocket/blob/develop/inc/classes/dependencies/wp-media/background-processing/wp-background-process.php The cron call `handle_cron_healthcheck()` passes some code (in the same file)...

@piotrbak Thanks for the update. I can confirm that the empty error messages no longer occur.

No, unfortunately not. We're using the latest version `4.3.9`.

I've found the following file: https://github.com/outlandishideas/wpackagist/blob/develop/src/Entity/Plugin.php There it states that if only the trunk gets updated wpackagist will create those timestamp urls. So could you please check again in the...

I think I found it: https://github.com/outlandishideas/wpackagist/blob/develop/src/Service/Update.php#L115 If the current version (in this case 4.14.1) doesn't exist as tag (and it doesn't) the trunk will be used for this: https://plugins.trac.wordpress.org/browser/cf7-grid-layout/#tags/ So...

I think there are some separate aspects to discuss and most of them are not related to WPackagist. Related to WPackagist: - As described above I'm not sure whether the...

Sorry, I misunderstood your tag handling. When I understand it correctly you update the minor tag version with the latest patch release. This reminds me of Docker hub where besides...

> > applying patches to a minor version release would lead to issues as they wouldn't get picked up by Composer installations automatically. Instead there's another race condition happening: Dev...

Some additions regarding "is it allowed to overwrite tags". SemVer which is the basis for Composer and recommended by WP states: https://semver.org/#spec-item-3 > Once a versioned package has been released,...

I've checked our projects for trunk installs of plugins and are quite surprised as how many different plugins (~18) this currently affects. I haven't checked them one by one whether...