6.14.0 Release September 15, 2026

• New: Add parallel part upload and merge support for Remote Sync Push. (Pro)
• Fix: Block IPv6 and DNS-rebinding bypasses of the backup download SSRF filter.
• Fix: Enable the Start Upload button when a storage is selected in the Upload Backup to Cloud popup.
• Fix: Generate job IDs with a secure random source so log stream tokens cannot be guessed.
• Fix: Include schemes in copied backup links and CLI restore commands.
• Fix: Let the subsites of a multisite use the WP Staging Pro licence activated in the network admin.
• Fix: Preserve native Element.prototype.closest and only polyfill it when missing.
• Fix: Prevent staging prefix reuse from destroying another staging site.
• Fix: Redact the installation root inside failed-move warnings.
• Fix: Refuse an invalid database table prefix when a staging site is saved, so pushing or resetting it cannot fail on it later.
• Fix: Reject invalid cloud download filenames before writing to the backups folder. (Pro)
• Fix: Remove every trailing issue reference from a changelog line before it appears in the newsfeed.
• Fix: Render the staging delete modal when the staging database is unreachable.
• Fix: Reopen the Upload Backup to Cloud popup after connecting a new cloud storage.
• Fix: Report the latest log line, not the whole log, when a job responds before it has logged anything.
• Fix: Stop logging a throttled request as an error during a healthy job.
• Fix: Stop the backup schedule cron event from flooding the error log when WordPress cannot save the cron option, and prevent copied network schedules from running on other sites without disabling cross-site backup plans.
• Fix: Stop the backups folder running scripts on Apache and IIS.
• Fix: Stop the fatal error in the network admin when WP STAGING Free and WP STAGING Pro are both active on the main site.
• Fix: Stop the scheduled-backup menu badge and cron warning from reporting a schedule row copied to a multisite subsite as overdue.
• Dev: Keep the release changelog intact when the prepare phase runs more than once.
• Dev: Post the WordPress.org release notes in every release run instead of leaving them as an optional follow-up.
• Dev: Say which environment an E2E pass ran in, so a green job no longer ends on an all-skipped summary.
• Dev: Write a release announcement covering Free and Pro once both versions are published, so the team is told what shipped.

Complete Changelog: https://wp-staging.com/wp-staging-pro-changelog/