Cache issue: ‘Rewrite & Republish’ scheduled via cron

When using ‘Rewrite & Republish’ in combination with a caching plugin like WP Super Cache, the cache for the original post is not cleared if the post is republished via a cron job. The issue seems to bee while the scheduled copy triggers the future_to_publish hook, the subsequent update of the original post via wp_update_post doesn’t involve a status change (it stays ‘publish’). Consequently, most caching plugins fail to detect that the content has changed. While the provided duplicate_post_after_republish hook allows us to implement a custom workaround, I strongly believe that native support for common caching mechanisms should be integrated into the core plugin. Handling cache invalidation is a critical part of a “republishing” workflow; without it, the feature is essentially incomplete for sites using standard caching setups.