Skip to content

feat: added Create Release Pipeline #438

Merged
Avijit-Microsoft merged 2 commits intodevfrom
ve-pipeline-changes
Aug 7, 2025
Merged

feat: added Create Release Pipeline #438
Avijit-Microsoft merged 2 commits intodevfrom
ve-pipeline-changes

Conversation

@Vemarthula-Microsoft
Copy link
Copy Markdown
Contributor

@Vemarthula-Microsoft Vemarthula-Microsoft commented Aug 6, 2025

Purpose

This pull request adds a new GitHub Actions workflow for automated release creation, tailored to the ve-pipeline-changes branch. The workflow uses semantic release tools to automate versioning, changelog generation, and GitHub release creation based on commit messages.

Release automation:

  • Added .github/workflows/Create-Release.yml to define a workflow that triggers on pushes to the ve-pipeline-changes branch, checks out the code, and runs semantic-release with custom commit type sections for release notes.
  • Configured permissions and environment variables to enable the workflow to create releases and write to pull requests.
  • Integrated the codfish/semantic-release-action with plugins for commit analysis, release notes generation, and GitHub release publishing, using the conventionalcommits preset and custom changelog sections.

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • ...

Other Information

@Avijit-Microsoft Avijit-Microsoft merged commit 789af06 into dev Aug 7, 2025
5 checks passed
@github-actions
Copy link
Copy Markdown

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@Prajwal-Microsoft Prajwal-Microsoft deleted the ve-pipeline-changes branch October 9, 2025 02:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants