Skip to content

Update release modification guidelines in documentation #3250

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MissedTheMark wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Update release modification guidelines in documentation #3250

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
63972e5
Update release modification guidelines in documentation
MissedTheMark Jul 21, 2026
a83a6f0
Update release snapshot change guidelines
MissedTheMark Jul 21, 2026
5002b21
Update deployment process guidelines in documentation
MissedTheMark Jul 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions src/pages/docs/best-practices/deployments/releases-and-deployments.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,17 +44,17 @@ 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
- Version number

However, you cannot change the following 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.

- Channel
- Deployment Process
You cannot change the deployment process in the release snapshot.

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

Expand Down
Loading