← All field notes

A security update lane still needs clear approval rules

A security release deserves prompt attention, but “security” is not permission to ignore every other control. Define the rule before an alert arrives.

  • Choose whether the site allows automatic security updates.
  • Check whether the release is applicable to the installed version.
  • Keep breaking-change approval requirements visible.
  • Review the operation result and follow up when the host or a license blocks the install.

IrmaWP can queue detected security releases without waiting for a maintenance window when that automation is enabled. A queued update is not proof that the site has already been patched.

Related guide: WordPress update controls.


Have a correction or a workflow we should cover? Tell the IrmaWP team.