Stillgate 0.1.1

Stillgate 0.1.1 is the rename and correction release for the plugin previously published as Deployment Guard. It is not a feature release.

Changed

• Renamed to Stillgate — Editorial Freeze for Deployments. The slug, text domain, main file (stillgate.php) and distribution folder are now stillgate. wp deployment-guard is now wp stillgate (there is no alias), and the settings screen is Tools > Stillgate (tools.php?page=stillgate).
• Stored identifiers are unchanged, so existing sites keep their configuration, activity log and bypass roles: the deployment_guard_state and deployment_guard_history options, the deployment_guard_bypass capability, DEPLOYMENT_GUARD_FORCE, and every deployment_guard_* hook, filter and REST error code.
• The classic admin notice now appears only on the dashboard and on screens that list or edit protected content (including custom post types and taxonomies). It explains how the freeze ends and disappears when it does.

Added

• Safe coexistence with the earlier release: Stillgate stays passive, and says so on the Plugins screen, if Deployment Guard is still active. While Stillgate is running, deleting Deployment Guard no longer erases the shared freeze configuration, activity log or bypass capability grants.

Upgrading from Deployment Guard 0.1.0

1. Install stillgate.zip but do not activate it yet.
2. Deactivate Deployment Guard (this ends a freeze that is currently active).
3. Activate Stillgate.
4. Delete the old Deployment Guard copy while Stillgate is active. Do not delete it while Stillgate is inactive: that erases the shared settings.

Requirements

WordPress 6.6+ and PHP 8.1+. GPL-2.0-or-later. No telemetry and no outbound HTTP requests.

Installation

Download stillgate.zip below and upload it under Plugins > Add New > Upload Plugin, or unzip it into wp-content/plugins/.

SHA-256: e3c245fc0167ca8c82c42df316133c6d50d06ab8ff1366ee4b3ee9da9047d2dd

Full details: CHANGELOG.md.

Deployment Guard 0.1.0

Initial release of Deployment Guard, which locks editorial changes during deployments and migrations while the public site stays online.

Features

• Manual editorial freeze from Tools > Deployment Guard or WP-CLI, and scheduled freeze windows evaluated against the site timezone on every relevant request (not dependent on WP-Cron).
• Content write protection in classic wp-admin and the block editor: posts, pages, custom post types, revisions, taxonomies and terms, media, navigation menus, widgets and the Customizer.
• REST API write protection (HTTP 423, error code deployment_guard_active) and XML-RPC write protection for content-changing methods; read-only requests are untouched.
• deployment_guard_bypass capability, granted to roles with manage_options on activation and checked independently of role names.
• WP-CLI commands other than wp deployment-guard are blocked from changing protected content during a freeze (use --user=<account with bypass> for an intentional change), and scheduled posts of protected types are held: they stay scheduled and publish normally after the freeze ends.
• wp deployment-guard status|enable|disable|schedule.
• Admin notice during a freeze (classic screens and block editor), settings screen with a bounded activity log, per-site Multisite operation, and a DEPLOYMENT_GUARD_FORCE constant to force the freeze on or off.

Requirements

WordPress 6.6+ and PHP 8.1+. GPL-2.0-or-later. No telemetry and no outbound HTTP requests.

Installation

Download deployment-guard.zip below and upload it under Plugins > Add New > Upload Plugin, or unzip it into wp-content/plugins/.

SHA-256: 3d1a7f07a42caeca3e19175ccb6d1388d30a63f9004240ccae7f61e961903956

Known limitations

The freeze works through WordPress's own entry points, capability checks and content functions. Direct database changes and third-party code that writes content without capability checks are outside what it can block. See the documented limitations.

Full details: CHANGELOG.md.