Bug fix: Governance gate no longer fires during node deletion
PillarShield's publish-gate logic could be triggered when deleting a node because Drupal's entity delete lifecycle may internally fire entity_presave (e.g. during revision cleanup with content moderation). This caused unnecessary SaaS API calls, confusing violation error messages on successful deletes, and in some configurations could block deletion entirely via EntityStorageException.
This release fixes a critical issue where blocked content could still be published on its initial save due to conflicts with the Content Moderation module.
Fixes non-moderated live content behavior: when a published node (status=1) fails governance on save, the module now blocks the save and keeps the currently published content unchanged (no automatic unpublish).
Continues to enforce governance for publish-gate transitions and for edits to already-live content, with Content Moderation preserving draft/non-live revisions when blocked.
Initial stable release of PillarShield for Drupal 10/11.
Adds integration with the PillarShield SaaS governance service to evaluate content during save/publish workflows and enforce allow/warn/block decisions based on configuration.