feat: added Create Release Pipeline #438
Merged
Avijit-Microsoft merged 2 commits intodevfrom Aug 7, 2025
Merged
Conversation
Avijit-Microsoft
approved these changes
Aug 7, 2025
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Purpose
This pull request adds a new GitHub Actions workflow for automated release creation, tailored to the
ve-pipeline-changesbranch. The workflow uses semantic release tools to automate versioning, changelog generation, and GitHub release creation based on commit messages.Release automation:
.github/workflows/Create-Release.ymlto define a workflow that triggers on pushes to theve-pipeline-changesbranch, checks out the code, and runs semantic-release with custom commit type sections for release notes.codfish/semantic-release-actionwith plugins for commit analysis, release notes generation, and GitHub release publishing, using theconventionalcommitspreset and custom changelog sections.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information