Update GitHub release task to not create a change log #1172
Conversation
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
SteveL-MSFT
approved these changes
Oct 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
PR Summary
This pull request makes adjustments to the release pipeline configuration in
.pipelines/DSC-Official.yml, specifically around how changelogs are handled during release creation. The main change is that changelogs will no longer be automatically generated and included in GitHub releases.Release pipeline configuration changes:
ChangeLogCompareToReleasevariable based on whether the release is a pre-release or stable release. This means the pipeline no longer dynamically determines which previous release to compare for changelog generation.addChangeLogtofalseand removing related changelog configuration options.PR Context