TwinCraft AutoGuard

1.4.1

• Fixed: WordPress core updates were still occasionally logged as “Failed” (with a false alarm email) even when the update genuinely succeeded. WordPress’s own automatic-update skin can accumulate non-fatal feedback messages during core’s multi-step update process, which were being misread as real errors. A proven version increase on disk is now the authoritative signal, overriding a noisy report either way — not just when a failure was reported. Also added a more reliable, independent way of capturing core’s version right before an automatic update cycle starts, since WordPress’s internal hook structure for core has shifted across versions (e.g. the 6.3+ rollback/temp_backup mechanism).

1.4.0

• Added: a one-time welcome popup right after activation, prompting a Diagnostics check in a couple of clicks. This surfaces the most common cause of “nothing is updating” (something outside the plugin silently blocking WordPress’s background updater) before it causes confusion, rather than leaving it to be discovered later.

1.3.4

• Fixed: two situations where a genuinely successful update was incorrectly logged as “Failed” and triggered a false failure email. First, background auto-updates (especially WordPress core) can retry internally — a failure signal from an earlier attempt could get attached even though a later retry in the same cycle actually succeeded; the plugin now trusts a proven version increase on disk over a noisy failure report. Second, updating something that’s already on the latest version (a normal no-op) was being flagged as a failure just because no version change was detected; it’s no longer treated as an error unless WordPress itself actually reported one.

1.3.3

• Updated Plugin URI to the live landing page at twincraftstudio.com/plugins/twincraft-autoguard/, now that it’s published under the new name.

1.3.2

• Fixed: WordPress core and theme updates were sometimes logged as “Failed” even though they succeeded. Verification was comparing against $wp_version and wp_get_theme(), both of which can hold outdated values in memory for the rest of the same request. Verification now reads the actual version straight from the file on disk (wp-includes/version.php for core, style.css for themes) instead.

1.3.1

• Fixed: the Diagnostics page no longer shows the “something is blocking updates” warning just because there’s nothing to update right now. “No updates currently available” and “Plugins toggle is off” are informational, not blockers, and no longer trigger the warning banner or the daily health-check email.