Add previous channel release version check #27
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: v.oleynikov <vasily.oleynikov@flant.com>
AleksZimin
reviewed
Apr 12, 2024
AleksZimin
reviewed
Apr 12, 2024
AleksZimin
reviewed
Apr 12, 2024
Signed-off-by: Aleksandr Zimin <alexandr.zimin@flant.com>
AleksZimin
approved these changes
Apr 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We need only sequential release deploy to channels
Why do we need it, and what problem does it solve?
We must prevent non-sequential release deploy
What is the expected result?
Correct previous channel release check
Checklist