From 63972e57f8e44c1c5c289b477f764adb648e422e Mon Sep 17 00:00:00 2001 From: Mark Coafield <46470837+MissedTheMark@users.noreply.github.com> Date: Tue, 21 Jul 2026 16:18:52 +1000 Subject: [PATCH 1/3] Update release modification guidelines in documentation Removed extra "to", and updated the list of unchangeable elements on a release. --- .../best-practices/deployments/releases-and-deployments.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/docs/best-practices/deployments/releases-and-deployments.md b/src/pages/docs/best-practices/deployments/releases-and-deployments.md index b7f1638623..deaff97994 100644 --- a/src/pages/docs/best-practices/deployments/releases-and-deployments.md +++ b/src/pages/docs/best-practices/deployments/releases-and-deployments.md @@ -48,13 +48,13 @@ You can update the following in a release: - Package version - Release notes - Variables +- Channel However, you cannot change the following in the release snapshot: -- Channel - Deployment Process -Never to modify a release unless it is absolutely necessary. A release represents a snapshot in time, and it should be the same when deploying to the different stages or environments in your pipeline. Changing it after the fact can lead to unpredictable results. +Never modify a release unless it is absolutely necessary. A release represents a snapshot in time, and it should be the same when deploying to the different stages or environments in your pipeline. Changing it after the fact can lead to unpredictable results. ## Deploying a release From a83a6f0305a9cb1e0110c4d50a6e4da21a3543ea Mon Sep 17 00:00:00 2001 From: Mark Coafield <46470837+MissedTheMark@users.noreply.github.com> Date: Tue, 21 Jul 2026 16:20:45 +1000 Subject: [PATCH 2/3] Update release snapshot change guidelines Clarified the items that can and cannot be changed in a release snapshot. --- .../deployments/releases-and-deployments.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/src/pages/docs/best-practices/deployments/releases-and-deployments.md b/src/pages/docs/best-practices/deployments/releases-and-deployments.md index deaff97994..a01e3faed3 100644 --- a/src/pages/docs/best-practices/deployments/releases-and-deployments.md +++ b/src/pages/docs/best-practices/deployments/releases-and-deployments.md @@ -44,15 +44,13 @@ The release includes a snapshot containing the deployment process, variables (in You can update the following in a release: -- Version number +- Channel - Package version - Release notes - Variables -- Channel - -However, you cannot change the following in the release snapshot: +- Version number -- Deployment Process +You cannot, however, change the deployment process in the release snapshot. Never modify a release unless it is absolutely necessary. A release represents a snapshot in time, and it should be the same when deploying to the different stages or environments in your pipeline. Changing it after the fact can lead to unpredictable results. From 5002b218b5602172bdcfb9c7d32141a7968b4003 Mon Sep 17 00:00:00 2001 From: Mark Coafield <46470837+MissedTheMark@users.noreply.github.com> Date: Tue, 21 Jul 2026 16:31:30 +1000 Subject: [PATCH 3/3] Update deployment process guidelines in documentation Clarified restrictions on changing deployment processes and emphasized the importance of maintaining release integrity. --- .../best-practices/deployments/releases-and-deployments.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/pages/docs/best-practices/deployments/releases-and-deployments.md b/src/pages/docs/best-practices/deployments/releases-and-deployments.md index a01e3faed3..fc8baa8f63 100644 --- a/src/pages/docs/best-practices/deployments/releases-and-deployments.md +++ b/src/pages/docs/best-practices/deployments/releases-and-deployments.md @@ -50,7 +50,9 @@ You can update the following in a release: - Variables - Version number -You cannot, however, change the deployment process in the release snapshot. +Please note that changing the channel of a release is only allowed where all the steps previously applicable (with respect to any channel filters) will still be applicable with the new channel. + +You cannot change the deployment process in the release snapshot. Never modify a release unless it is absolutely necessary. A release represents a snapshot in time, and it should be the same when deploying to the different stages or environments in your pipeline. Changing it after the fact can lead to unpredictable results.