From b494163fe3a093b16dfb25a85985524544bd6665 Mon Sep 17 00:00:00 2001 From: Ocneanu Vlad Date: Tue, 4 Aug 2026 13:34:03 +0300 Subject: [PATCH] Clarify that a release publishes the latest draft, not a snapshot A release action stores only a reference to an entry (content type, document ID, locale and action type), so publishing a release resolves each entry's current draft at publish time. Editing a draft after adding it to a release therefore changes what gets published, and a release cannot be pinned to a specific version. This was not documented anywhere on the Releases page, and is a common point of confusion for content managers using scheduled releases. Co-Authored-By: Claude Opus 5 (1M context) --- docusaurus/docs/cms/features/releases.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docusaurus/docs/cms/features/releases.md b/docusaurus/docs/cms/features/releases.md index 306bdc72b0..130270caca 100644 --- a/docusaurus/docs/cms/features/releases.md +++ b/docusaurus/docs/cms/features/releases.md @@ -104,6 +104,10 @@ Since publishing an entry with a release means turning a draft entry into a publ - Adding content to a release requires the appropriate permissions for the Content-Releases plugin (see [configuring administrator roles](/cms/features/users-permissions)). ::: +:::caution +A release stores a reference to an entry, not a copy of its content. If the draft is edited after being added to a release, the release will publish the latest saved version of the draft, not the version that existed when the entry was added. A release cannot be pinned to a specific version of an entry. To publish an earlier version, restore it as the draft using [Content History](/cms/features/content-history) before the release is published. +::: + #### One entry at a time **Path:** Edit view of the Content Manager