Affinity Guard 1.0.1

Points self updates at this organisation, following the move from bmx269/affinity-guard.

The release source is compiled into the plugin rather than configured, so an install left on 1.0.0 will stop updating itself once a repository of the old name exists again — a fork recreates that name, and forks do not inherit releases. Copy affinity-guard.php from this release over any 1.0.0 install rather than waiting for it to update on its own.

No behaviour, constants or hooks changed. See CHANGELOG.md.

Affinity Guard 1.0.0

First release under the name Affinity Guard.

Lets WordPress install its own core security releases on sites deployed from git, by answering the automatic_updates_is_vcs_checkout filter that otherwise blocks every background update when a .git directory is found.

Install: copy affinity-guard.php into wp-content/mu-plugins/. No activation, no settings.

Defaults: enabled, minor core releases only, self updating within the 1.x line.

Configure in wp-config.php:

define( 'AFFINITY_GUARD_ENABLED', false );      // true (default) | false
define( 'AFFINITY_GUARD_UPDATES', 'major' );    // 'minor' (default) | 'major' | 'dev'
define( 'AFFINITY_GUARD_SELF_UPDATE', false );  // true (default) | false

See the README for what minor, major and dev mean, the hook API for other security tooling, and the self update safety checks. Full notes in CHANGELOG.md.