chore(ci): add automatic github release#2291
Merged
Merged
Conversation
Signed-off-by: Maksim Fedotov <maksim.fedotov@flant.com>
Signed-off-by: Maksim Fedotov <maksim.fedotov@flant.com>
Signed-off-by: Maksim Fedotov <maksim.fedotov@flant.com>
Signed-off-by: Maksim Fedotov <maksim.fedotov@flant.com>
Signed-off-by: Maksim Fedotov <maksim.fedotov@flant.com>
Signed-off-by: Maksim Fedotov <maksim.fedotov@flant.com>
universal-itengineer
approved these changes
Apr 29, 2026
This file contains hidden or 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
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
Add automatic GitHub release handling to the
Deploy Prodworkflow and extend Loop notifications with GitHub release status.Why do we need it, and what problem does it solve?
Deploy Prodalready publishes module versions to release channels, but GitHub releases are still created separately. This change lets the workflow automatically prepare a GitHub release from the generated changelog PR for the same version.For testing, the release creation step is temporarily switched to dry-run mode and Loop notifications are sent to the test webhook channel. This makes it possible to validate PR lookup, release notes generation, and notification formatting without creating a real GitHub release or posting to the production Loop channel.
What is the expected result?
Deploy Prodwithrelease_to_github=truefor a tag that has exactly one mergedchangelogPR with milestone equal to the tag.gh release createcommand it would execute.LOOP_TEST_CHANNELand includes a separateGitHub releasesection.check_only=trueorrelease_to_github=falseskips the GitHub release step.Checklist
Changelog entries