readme.txt — WP STAGING – WordPress Backups, Restore, Migration & Clone 4.11.1

wp-staging / readme.txt

wp-staging Last commit date

Backend 4 days ago Backup 4 days ago Basic 1 week ago Component 1 week ago Core 4 days ago Framework 4 days ago Frontend 1 week ago Notifications 1 week ago Staging 4 days ago assets 4 days ago languages 1 week ago resources 1 week ago vendor_wpstg 1 week ago views 4 days ago CONTRIBUTING.md 2 years ago Deactivate.php 1 week ago README.md 5 months ago SECURITY.md 1 month ago autoloader.php 1 week ago bootstrap.php 1 week ago commonBootstrap.php 1 week ago constantsFree.php 4 days ago freeBootstrap.php 1 week ago install.php 1 week ago opcacheBootstrap.php 4 days ago readme.txt 4 days ago runtimeRequirements.php 1 week ago uninstall.php 4 days ago wp-staging-error-handler.php 1 week ago wp-staging.php 4 days ago

readme.txt

350 lines

1	=== WP STAGING - WordPress Backups, Restore, Migration & Clone ===
2
3	Contributors: WP-Staging, WPStagingBackup, ReneHermi, lucatume, lucasbustamante, alaasalama, fayyazfayzi
4	Donate link: https://wp-staging.com/backup-wordpress
5	License: GPLv2 or later
6	License URI: https://www.gnu.org/licenses/gpl-2.0.html
7	Tags: backup, wordpress backup, restore, move, transfer
8	Requires at least: 3.6
9	Tested up to: 7.1
10	Stable tag: 4.11.1
11	Requires PHP: 7.0
12
13	WordPress backup plugin: backups, restore & migration in minutes. Clone or duplicate your site, test updates on a staging copy. 100% unit-tested.
14
15	== Description ==
16
17	<h3>WordPress Backup, Restore, Staging, Cloning & Migration — All in One</h3>
18
19	WP STAGING is the all-in-one WordPress backup, restore, staging, cloning, and migration plugin, built for professional workflows with 100% unit-tested code, thousands of automated tests, and extensive end-to-end testing across supported PHP versions.
20
21	Create a full backup or an exact clone or copy of your website in minutes. Use it to duplicate your site, test plugin and theme updates safely, restore your site when needed, move or migrate WordPress to another server, transfer your site to a new host, or build a staging copy before making changes. WP STAGING also works as a WordPress duplicator, so you do not need a separate duplicator plugin to copy your website.
22
23	WP STAGING reliably backs up, clones, and migrates WooCommerce stores too, including orders, products, and customer data.
24
25	WP STAGING is developed in Germany and designed for agencies, developers, and businesses that need reliable WordPress backup, recovery, staging, restore, and migration workflows.
26
27	[WP STAGING \| PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") also includes advanced workflows such as [Remote Sync](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/ "Remote Sync - Pull a WordPress Site from One Server to Another"), which lets you pull a WordPress site securely from one server to another using an API key, and [WP STAGING CLI](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress"), which can turn a WP STAGING backup into a local Docker-based development site.
28
29	All data stays on your server unless you choose a transfer or remote storage workflow. WP STAGING is designed for speed, reliability, and low-resource environments, including shared hosting.
30
31	WP STAGING automatically performs search and replace for links and paths during cloning, backup, restore, and migration workflows.
32
33	This staging and backup plugin can clone your website quickly and efficiently, even if it is running on a weak shared hosting server.
34
35	[vimeo https://vimeo.com/999447985]
36
37	== Frequently Asked Questions ==
38
39	= Why should I use a staging site and backup workflow? =
40
41	Plugin updates, theme changes, and custom code should be tested before they reach your live site. A staging workflow lets you clone your production website, test changes safely, and keep a working backup ready in case something goes wrong. Safe updates and update testing on a staging copy protect your live site from broken releases.
42
43	Usually, it is best to run the staging site on an environment as close as possible to the production server. That is the best way to catch compatibility issues before they affect your live site.
44
45	WP STAGING combines backup, restore, staging, and migration in one workflow, so you can protect your live website, reduce downtime risk, and ship changes with more confidence.
46
47	= Is WP STAGING a backup plugin? =
48
49	Yes. WP STAGING started as a staging plugin and grew into a complete WordPress backup plugin, with restore, staging, cloning, and migration in one tool.
50
51	Even the free version lets you create backups and restore them when needed. [WP STAGING \| PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") adds more advanced backup workflows, cloud storage destinations, migration tools, and developer-focused features.
52
53	= How is WP STAGING different from other backup plugins? =
54
55	WP STAGING combines backup, restore, staging, cloning, and migration in one workflow. While many backup plugins focus mainly on archive-based backups or simple migration, WP STAGING also helps you create a working staging copy, test updates safely, and restore your site when needed.
56
57	Some backup plugins focus mainly on creating backup archives, while WP STAGING also creates working staging copies for safer testing and rollback workflows. This is especially useful when you want production-like validation before pushing changes live.
58
59	Some backup plugins may not fully support custom tables in all scenarios. WP STAGING is designed to work reliably with staging workflows and custom table prefixes used by its own cloned environments.
60
61	[WP STAGING \| PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") also includes advanced workflows such as [Remote Sync](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/ "Remote Sync - Pull a WordPress Site from One Server to Another") and [WP STAGING CLI](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress"), which can turn a backup into a local Docker-based development site. That makes WP STAGING especially attractive for developers, agencies, and site owners who want more than a basic backup plugin.
62
63	= How do I back up and restore a WordPress site? =
64
65	After installing WP STAGING, go to the backup section in the plugin and create a full-site backup. You can then restore that backup if a plugin update, theme change, deployment, or unexpected issue breaks your site.
66
67	WP STAGING is designed to make backup and restore simple, even on shared hosting and large WordPress installations.
68
69	= What is Remote Sync in WP STAGING Pro? =
70
71	Remote Sync is a Pro feature that lets you pull a WordPress site securely from one server to another using an API key. Instead of manually exporting databases and copying files, you connect the two sites and start the sync from inside WP STAGING.
72
73	This is especially useful for agencies, developers, and site owners who want a faster and more reliable workflow for moving content between WordPress installs.
74
75	Learn more:
76	[Remote Sync: Pull a WordPress Site from One Server to Another](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/ "Remote Sync - Pull a WordPress Site from One Server to Another")
77
78	= How can I turn a backup into a local Docker development site? =
79
80	[WP STAGING \| PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") includes access to [WP STAGING CLI](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress"), which can turn a WP STAGING backup into a local Docker-based WordPress site with one command.
81
82	This is ideal for debugging, QA, development, and reproducing client issues locally. It helps you create repeatable local environments without building custom Docker setups for every project.
83
84	Learn more:
85	[WP STAGING CLI – Upgrade Now](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Upgrade Now")
86
87	= How do I move, migrate, or transfer a WordPress site to a new host? =
88
89	[WP STAGING \| PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") includes migration and transfer workflows that help you move a WordPress website to another host, transfer your WordPress site to a new host, change the domain, or move to another server. You can move your website between hosts without manual database exports.
90
91	If you want a guided step-by-step walkthrough, see:
92	[How to Migrate Your WordPress Site to a New Host](https://wp-staging.com/docs/how-to-migrate-your-wordpress-site-to-a-new-host/ "How to Migrate Your WordPress Site to a New Host")
93
94	= How do I duplicate or clone a WordPress site? =
95
96	WP STAGING works as a WordPress duplicator: it can duplicate or clone a WordPress site in a few clicks and create an exact copy of your site for testing, development, or as a safety net. Duplication runs in the background, so you can duplicate even large WordPress sites on shared hosting. If you have used a plugin like Duplicator before, WP STAGING covers the same clone and copy workflows and adds backup, restore, and staging.
97
98	= Is WP STAGING a good Duplicator alternative? =
99
100	Yes. If you are looking for a Duplicator alternative, WP STAGING covers the same use cases: duplicate a WordPress site, create a full-site copy, and move or transfer it to another host. In addition to the duplicator workflow, you get one-click staging sites, scheduled backups, and restore in the same plugin.
101
102	= Why do I need a backup plugin at all? =
103
104	Consistent website backups are the foundation of a robust disaster recovery strategy. They protect your website against failed updates, user mistakes, malware cleanup, hosting issues, hardware failures, software malfunctions, and data loss.
105
106	Backups should include website files, databases, user data, and configuration data. A combination of full backups and incremental backups can improve storage efficiency while keeping restore points current.
107
108	If your website generates leads, sales, traffic, or customer trust, regular backups are not optional. A reliable backup, restore, and recovery workflow lets you roll back your WordPress site and can save hours of downtime and expensive recovery work.
109
110	= Can I activate permalinks on the staging site? =
111
112	Permalinks are disabled on the staging site after the first cloning process.
113
114	Read this guide to activate permalinks on your staging site:
115	[Activate Permalinks on the Staging Site](https://wp-staging.com/docs/activate-permalinks-staging-site/ "Activate Permalinks on the Staging Site")
116
117	= I cannot log in to the staging or backup site =
118
119	If you use a security plugin such as Wordfence, iThemes Security, All In One WP Security & Firewall, or a plugin that hides the default WordPress login URL, make sure you are running the latest version of WP STAGING.
120
121	If you still cannot log in, go to WP STAGING > Settings and disable WP STAGING extra authentication. Your admin dashboard will still remain protected.
122
123	= Can I just use my local WordPress development system for testing and backup? =
124
125	You can always test your website locally, but if your local hardware and software environment is not an exact clone of your production server, there is no guarantee that every aspect of your local copy will behave the same way.
126
127	Differences in PHP version, server stack, memory, CPU performance, and filesystem behavior can all lead to unexpected results on production. That is why staging on infrastructure close to production remains valuable.
128
129	[WP STAGING \| PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") also gives you a more advanced local workflow through [WP STAGING CLI](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress"), which can turn a backup into a local Docker-based development site.
130
131	= Is WP STAGING available in multiple languages? =
132
133	Yes. WP STAGING is available in multiple languages, and several translations are already complete or nearly complete.
134
135	You can view translated plugin pages here:
136
137	[English](https://wordpress.org/plugins/wp-staging/ "WP STAGING on WordPress.org")
138	[French](https://fr.wordpress.org/plugins/wp-staging/ "WP STAGING en Français")
139	[German](https://de.wordpress.org/plugins/wp-staging/ "WP STAGING auf Deutsch")
140	[Spanish](https://es.wordpress.org/plugins/wp-staging/ "WP STAGING en Español")
141	[Croatian](https://hr.wordpress.org/plugins/wp-staging/ "WP STAGING na hrvatskom")
142	[Dutch](https://nl.wordpress.org/plugins/wp-staging/ "WP STAGING in het Nederlands")
143	[Finnish](https://fi.wordpress.org/plugins/wp-staging/ "WP STAGING suomeksi")
144	[Greek](https://el.wordpress.org/plugins/wp-staging/ "WP STAGING στα Ελληνικά")
145	[Hungarian](https://hu.wordpress.org/plugins/wp-staging/ "WP STAGING magyarul")
146	[Indonesian](https://id.wordpress.org/plugins/wp-staging/ "WP STAGING dalam Bahasa Indonesia")
147	[Italian](https://it.wordpress.org/plugins/wp-staging/ "WP STAGING in Italiano")
148	[Persian](https://fa.wordpress.org/plugins/wp-staging/ "WP STAGING به فارسی")
149	[Polish](https://pl.wordpress.org/plugins/wp-staging/ "WP STAGING po polsku")
150	[Portuguese (Brazil)](https://br.wordpress.org/plugins/wp-staging/ "WP STAGING em Português do Brasil")
151	[Russian](https://ru.wordpress.org/plugins/wp-staging/ "WP STAGING по-русски")
152	[Turkish](https://tr.wordpress.org/plugins/wp-staging/ "WP STAGING Türkçe")
153	[Vietnamese](https://vi.wordpress.org/plugins/wp-staging/ "WP STAGING bằng Tiếng Việt")
154
155	If you want to help improve translations, please get in touch with us through the support forum.
156
157	= Can I give feedback for WP STAGING? =
158
159	Yes. If something does not work as expected, please open a support request and describe the issue in as much detail as possible.
160
161	We continuously improve WP STAGING based on user feedback, real-world hosting environments, and developer use cases.
162
163	Open support:
164	[WP STAGING Support Forum](https://wordpress.org/support/plugin/wp-staging/ "WP STAGING Support Forum")
165
166	== WP STAGING FREE - BACKUP & STAGING FEATURES ==
167
168	* Clone the entire production site into a subdirectory like example.com/staging-site.
169	* High-performance backup and cloning, even for websites with very large databases.
170	* Create full or partial backups — full-site backup, database-only, or files-only backups.
171	* Scheduled backups with automatic daily backups.
172	* Easy to use: create a clone or backup in one click.
173	* Efficient background processing without slowing down your website.
174	* No Software as a Service and no external account required.
175	* All your data stays on your server. Your data belongs to you only.
176	* No server timeouts on huge websites or weak servers.
177	* Fast backup, clone, and restore workflows depending on site size and server resources.
178	* Use the clone as part of your backup and update strategy.
179	* Only administrators can access the cloned or backup website.
180	* SEO-friendly staging sites with login protection and no-index handling.
181	* The admin bar on the staging / backup website is orange colored and shows when you work on the staging site.
182	* Extensive logging features.
183	* Supports Apache, Nginx, Microsoft IIS, and LiteSpeed Server.
184	* Every release passes extensive automated tests to keep the plugin robust, reliable, and fast.
185	* Fast and professional support team.
186
187	== WP STAGING \| PRO - BACKUP & STAGING FEATURES ==
188
189	The features below are available in [WP STAGING \| PRO](https://wp-staging.com/backup-pro-features "WP STAGING \| PRO Features").
190
191	* Remote Sync - Pull a WordPress site securely from one server to another.
192	* WP STAGING CLI - Turn a backup into a local Docker-based development site.
193	* Migrate and transfer WordPress to another host or domain.
194	* Push staging changes to production (staging to live), including plugins, themes, and media files, with one click.
195	* Clone a backup or staging site to a separate database.
196	* Choose a custom directory for a backup or cloned site.
197	* Select a custom subdomain destination like dev.example.com.
198	* Define user roles for accessing the clone or backup site. This can be clients or external developers.
199	* Multisite support for migration, backup, and cloning.
200	* Schedule recurring backups by time and interval.
201	* Download and upload backups to another server for migration and transfer.
202	* Backup retention settings.
203	* Custom backup names.
204	* Email notifications if a backup cannot be created.
205	* WordPress multisite backup and restore.
206	* Cloud backup, offsite backup, and remote backups to external storage providers.
207	* Backup to Google Drive.
208	* Backup to Amazon S3.
209	* Backup to (S)FTP.
210	* Backup to Dropbox.
211	* Custom backup folder destinations for cloud storage providers.
212	* Priority support.
213
214	== DOCUMENTATION ==
215
216	<strong>How to Backup and Restore WordPress</strong>
217	[Backup and Restore WordPress](https://wp-staging.com/docs/how-to-backup-and-restore-your-wordpress-website/ "Backup and Restore WordPress")
218
219	<strong>Backup & Transfer WordPress Site to Another Host</strong>
220	[How to Migrate Your WordPress Site to a New Host](https://wp-staging.com/docs/how-to-migrate-your-wordpress-site-to-a-new-host/ "How to Migrate Your WordPress Site to a New Host")
221
222	<strong>Remote Sync</strong>
223	[Pull a WordPress Site from One Server to Another](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/ "Remote Sync - Pull a WordPress Site from One Server to Another")
224
225	<strong>Local Docker Development with WP STAGING CLI</strong>
226	[WP STAGING CLI – Upgrade Now](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress")
227
228	<strong>All Backup Guides</strong>
229	[All Backup Guides](https://wp-staging.com/docs/category/backup-restore/ "All Backup Guides")
230
231	<strong>Working with Staging Sites</strong>
232	[Working with Staging Sites](https://wp-staging.com/docs/category/working-with-wp-staging/ "Working with Staging Sites")
233
234	<strong>FAQ for Backup & Cloning</strong>
235	[FAQ for Backup & Cloning](https://wp-staging.com/docs/category/frequently-asked-questions/ "Backup & Cloning FAQ")
236
237	<strong>Troubleshooting Backup & Cloning</strong>
238	[Troubleshooting Backup & Cloning](https://wp-staging.com/docs/category/troubleshooting/ "Troubleshooting Backup & Cloning")
239
240	== WP STAGING BACKUP & CLONING TECHNICAL REQUIREMENTS & INFORMATION ==
241
242	* Works on latest version of WordPress
243	* Minimum Supported WordPress Version 3.8
244	* Cloning and Backup work on all webhosts
245	* No extra libraries required
246	* Backup & cloning supports huge websites
247	* Custom backup format is much faster and smaller than any tar or zip compression
248	* Backup & cloning works in low memory & shared hosting environments
249
250	== SUPPORT ==
251
252	[WP STAGING Backup & Cloning](https://wp-staging.com/backup-wordpress "WP STAGING Backup & Cloning")
253
254	== Installation ==
255
256	= Installation via admin plugin search =
257
258	1. Go to Plugins > Add new. Select "Author" from the dropdown near search input.
259	2. Search for "WP STAGING". Searching for "WPStaging" in one word works as well.
260	3. Find "WP STAGING - WordPress Backup, Restore & Migration" and click the "Install Now" button.
261	4. Activate the plugin.
262	5. The plugin should be shown below settings menu.
263
264	= Admin Installer via zip =
265
266	1. Visit the Add New plugin screen and click the "Upload Plugin" button.
267	2. Click the "Browse..." button and select the zip file of our plugin.
268	3. Click "Install Now" button.
269	4. Once uploading is done, activate WP STAGING - WordPress Backup, Restore & Migration.
270	5. The plugin should be shown below the settings menu.
271
272	== Screenshots ==
273
274	1. Create new WordPress staging / backup site (Dark Mode)
275	2. Create new WordPress staging / backup site (Lite Mode)
276	3. Select name for staging / backup site (Lite Mode)
277	4. Create Full Site Backup (Dark Mode)
278	5. Create Full Site Backup (Lite Mode)
279	6. Cloning / backup processing (Dark Mode)
280	7. Backup Complete (Dark Mode)
281	8. Login to staging site
282	9. Staging demo site
283
284	== Changelog ==
285
286	= 4.11.1 =
287	* New: Show backup prompt before updating plugins, themes, or WordPress core. The recovery backup then runs in the background, and further updates queue behind it instead of asking again. #4028
288	* Enh: Allow the free version to back up other folders in the WordPress root directory. #5532
289	* Enh: Log the source and the destination table name while copying database tables, so the clone log no longer reads as if it copies staging tables. #5536
290	* Enh: Record a generic analytics event when an upgrade CTA is clicked, so the plugin side of the upgrade funnel can be compared with the website arrivals it produces. #5640
291	* Enh: Record a stable error code alongside the translated message so failure causes can be counted reliably. #5510
292	* Enh: Record whether a site still has WP STAGING, by noting in the anonymous usage data when the plugin is switched on or off, together with the reason given when switching it off. #5586
293	* Enh: Show the selected table count against the site prefix total when creating a staging site, so a plugin-heavy site no longer looks like it copies every database table. #5536
294	* Enh: Show the task-selector first run to every new single-site WP STAGING Free installation. #5646
295	* Fix: A backup request left over from a staging site that never finished no longer blocks the backup offer on the next staging site you create. #5618
296	* Fix: A backup schedule saved during the very minute it is set for now waits for its next occurrence, instead of being registered for a time that has just passed. #5617
297	* Fix: A backup that was still waiting or running when the first-run setup finished now starts and is reported as completed. #5577
298	* Fix: Cancel the backup scheduled after a staging site when that staging site creation is cancelled. #5737
299	* Fix: Convert a raw byte count to megabytes so the backup speed index is no longer always zero. #5590
300	* Fix: Drop the plugin dependencies from the shipped autoload classmap, which listed them at paths the build deletes. #5693
301	* Fix: Fail the restore when a database table rename fails, instead of reporting success on a half-swapped database. #5756
302	* Fix: Harden Classic staging row-exclusion filter values before SQL use. #5790
303	* Fix: Hide the "Create a Staging Site" onboarding card and post-backup offer on WordPress.com-hosted sites, which do not support staging. #5709
304	* Fix: Leave the hosting provider's own must-use plugin files out of the staging site when creating, updating and resetting it. #5643
305	* Fix: Pass a string to esc_attr in the onboarding capability icon. #5562
306	* Fix: Preserve unrelated subsite tables and user metadata during network site restores. (Pro) #5653
307	* Fix: Prevent an error when opening Push Changes with legacy settings. (Pro) #5829
308	* Fix: Provision a fresh test environment again when the WordPress template is a mounted folder. #5802
309	* Fix: Push summary now reflects the configured file-size limit instead of always showing 8 MB. #5560
310	* Fix: Refuse a second start that arrives while another request is already initializing a job, instead of letting both overwrite each other. #5516
311	* Fix: Reject non-stdClass serialized objects in the Pro search-replace routine to prevent PHP object injection, and add a sniff requiring an allowed_classes option on unserialize(). #5668
312	* Fix: Report a temporary or backup table that could not be dropped during cleanup, instead of logging it as deleted. #5756
313	* Fix: Report smart exclusions as switched off in WP Staging Free, where they never run, instead of on with nothing excluded. #5635
314	* Fix: Restore each multisite subsite with its own URLs instead of always the main site. #5633
315	* Fix: Restore the light icon when dark mode requests a dark variant that does not exist. #5739
316	* Fix: Retry a table drop that a lock blocked, and give the lock a bounded wait instead of holding the request open. #5756
317	* Fix: Scheduled backups are now included in the usage statistics, which previously only counted backups started by hand. #5507
318	* Fix: Show a notice instead of a critical error when the selected backup items contain no files. #5515
319	* Fix: Show the backup creation button in the Next-Gen staging site creation process modal and make the Pro Next-Gen engine release a queued backup once the staging site is created. #5776
320	* Fix: Skip the commit-lookup guardrail when the API does not answer, rather than failing it. #5673
321	* Fix: Stop a restore before it imports the database when tables of an earlier restore could not be removed. #5756
322	* Fix: Stop emitting a deprecation notice on PHP 8.4 and 8.5 for parameters that accept null. #5758
323	* Fix: Stop renaming a backup created on Windows from reporting it as damaged. #5768
324	* Fix: Stop sending Remote Sync analytics events before the job finishes, which left most syncs recorded without an outcome. #5504
325	* Fix: Stop the Network Admin staging page from getting stuck on unresolved analytics consent. #5628
326	* Fix: Stop the release publish phases from losing a successful prepare run. #5779
327	* Fix: Type the database rows WordPress 7.1 now describes precisely, so static analysis passes again. #5754
328	* Fix: Write one line terminator in the backup format on every platform, so a backup created on Windows matches the one created on Linux. #5768
329	* Dev: Add a shutdown-worktree skill that stops the containers before removing the folder. #5798
330	* Dev: Add the 2026-08-14 reading of the free_onboarding_v1 experiment with a D1 cut that matures before the 7-day windows close, and make the reading a one-command daily job. #5609
331	* Dev: Cancel a Fast tests run when a newer push supersedes it, and keep PHP 8.0 and 8.1 for the full matrix. #5786
332	* Dev: Fold the four cheap fast-test jobs into a single static_checks job. #5792
333	* Dev: Give the Playwright E2E jobs enough time to finish when the runner has to pull its Docker images first. #5824
334	* Dev: Give the Windows unit tests back the time they need to finish. #5806
335	* Dev: Keep the deploy API mu-plugin only in the wp-staging.com repo, so a copy carrying the object-cache flush that broke the 6.11.0 release cannot be uploaded to production again. #5741
336	* Dev: Move the skills to .agents so every agent can read them, not only Claude. #5733
337	* Dev: Raise the release pre-flight floor for the deploy API to 1.4.0, so a production rollback to a mu-plugin without the changelog-anchor guard blocks the release instead of corrupting the changelog page. #5799
338	* Dev: Raise the self-hosted GitHub Actions fleet on xsimulator.net from eight runners to twelve. #5789
339	* Dev: Say what make tests_guardrails checks, and cover the Makefile baseline comparison with its own test. #5780
340	* Dev: Stop running environment-independent e2e tests once per environment, and split the longest pro jobs. #5833
341	* Dev: Work through the classes the wpfree sieves deferred, and drop the transient users. #5703
342
343	WP STAGING Backup & Cloning \| Full changelog:
344	[https://wp-staging.com/wp-staging-changelog](https://wp-staging.com/wp-staging-changelog)
345
346	== Upgrade Notice ==
347
348	Compatible up to WordPress 7.0.
349	Many improvements for reliability and bug fixes. Please update to the latest version!
350