From a1b6f27261444b90aa914cc4cf61de684023331e Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Fri, 4 Sep 2026 01:44:51 +0000 Subject: [PATCH 1/2] Document release actions in audit logs Add release events (create, update, delete, trigger, entry add/change/remove, settings update) to the audit-logs event table, and add a dedicated section to the releases page explaining what is recorded and how to view it. Co-Authored-By: Claude Sonnet 4.6 --- docusaurus/docs/cms/features/audit-logs.md | 3 +++ docusaurus/docs/cms/features/releases.md | 25 ++++++++++++++++++++++ 2 files changed, 28 insertions(+) diff --git a/docusaurus/docs/cms/features/audit-logs.md b/docusaurus/docs/cms/features/audit-logs.md index a307ce542a..80a39ac4f6 100644 --- a/docusaurus/docs/cms/features/audit-logs.md +++ b/docusaurus/docs/cms/features/audit-logs.md @@ -51,6 +51,9 @@ The Audit Logs feature logs the following events: | Entry (draft/publish) | `create`, `update`, `delete`, `publish`, `unpublish` | | Media | `create`, `update`, `delete` | | Login / Logout | `success`, `fail` | +| Releases | `create`, `update`, `delete`, `trigger` | +| Release entries | `add`, `update`, `remove` | +| Release settings | `update` | | Role / Permission | `create`, `update`, `delete` | | User | `create`, `update`, `delete` | diff --git a/docusaurus/docs/cms/features/releases.md b/docusaurus/docs/cms/features/releases.md index 130270caca..36d47bcc15 100644 --- a/docusaurus/docs/cms/features/releases.md +++ b/docusaurus/docs/cms/features/releases.md @@ -216,3 +216,28 @@ Once a release is published, the release itself cannot be updated. You can not r dark: '/img/assets/releases/publish-release_DARK.png', }} /> + +### Audit logging of release actions + + + +Release actions are automatically captured in [Audit Logs](/cms/features/audit-logs) for Enterprise plan users. Every significant change to a release, its entries, or its settings produces a log entry — regardless of whether the action came from the admin panel or a scheduled job. + +The following actions are recorded: + +| Action | What is logged | +| --- | --- | +| Create release | The new release name, and whether it was scheduled. | +| Update release | The fields that changed (name, schedule date, timezone) and their previous and new values. No entry is created if nothing changed. | +| Delete release | The deleted release identifier. | +| Trigger release | The number of entries published or unpublished and the outcome: `success` or `failure` (error name only, no internal details). | +| Add entry to release | One log entry per entry added, with the content type, document ID, locale, and action type (`publish` or `unpublish`). | +| Change entry on release | The previous and new action type (`publish` ↔ `unpublish`). No entry is created if nothing changed. | +| Remove entry from release | The entry that was explicitly removed from the release. | +| Update release settings | The previous and new default timezone value. No entry is created if nothing changed. | + +Each log record includes the actor (user name, or `-` for scheduled triggers), the origin (`admin` for manual actions, `scheduler` for automatic ones), and the resource affected. To view release log entries, go to **Settings > Audit Logs** and look for entries prefixed with *release*. + +:::note +Deleting an entry or a locale that happens to be in a pending release does not create a "Remove entry from release" log. Only explicit removal is recorded. The delete action on the entry or locale itself is logged separately. +::: From df19de6576a626c686badfcbbd8421a3c8a00ed3 Mon Sep 17 00:00:00 2001 From: Pierre Wizla Date: Fri, 4 Sep 2026 09:48:29 +0200 Subject: [PATCH 2/2] Apply suggestion from @pwizla --- docusaurus/docs/cms/features/releases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docusaurus/docs/cms/features/releases.md b/docusaurus/docs/cms/features/releases.md index 36d47bcc15..8502a6bf34 100644 --- a/docusaurus/docs/cms/features/releases.md +++ b/docusaurus/docs/cms/features/releases.md @@ -221,7 +221,7 @@ Once a release is published, the release itself cannot be updated. You can not r -Release actions are automatically captured in [Audit Logs](/cms/features/audit-logs) for Enterprise plan users. Every significant change to a release, its entries, or its settings produces a log entry — regardless of whether the action came from the admin panel or a scheduled job. +Release actions are automatically captured in [Audit Logs](/cms/features/audit-logs) for Enterprise plan users. Every significant change to a release, its entries, or its settings produces a log entry, regardless of whether the action came from the admin panel or a scheduled job. The following actions are recorded: