Skip to content
This repository has been archived by the owner on May 3, 2022. It is now read-only.

Reject modifications to Release environment #357

Merged
merged 1 commit into from
Oct 12, 2020
Merged

Conversation

hihilla
Copy link
Contributor

@hihilla hihilla commented Oct 8, 2020

This is a cherry-pick of #340

A Release should be created only by modifying the Application object. That should be the only way for a user to create a new Release to roll out.
Older Release objects should never be modified. They are there so that a user can use them as a reference when reverting to an earlier release.

A Release should be created only by modifying the Application object. That should be the only way for a user to create a new Release to roll out.
Older Release objects should never be modified. They are there so that a user can use them as reference when reverting to an earlier release.
@hihilla hihilla force-pushed the hilla/cherry-pick-340 branch from 56be479 to 172ffb0 Compare October 12, 2020 12:15
@hihilla hihilla merged commit 0ae9519 into master Oct 12, 2020
@hihilla hihilla deleted the hilla/cherry-pick-340 branch October 12, 2020 13:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants