Use GitHub-generated release notes#56
Merged
juan-fernandez merged 1 commit intomainfrom Apr 27, 2026
Merged
Conversation
daniel-mohedano
approved these changes
Apr 27, 2026
juan-fernandez
added
the
semver-patch
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
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.
Summary
scripts/release-datadog-ci-bump.shto create releases with GitHub-generated release notes instead of a custom handwritten body.RELEASE.mdto document that releases now use GitHub-generated notes.Why
The current release script creates a minimal custom release body, which does not match the format GitHub generates when using the “Generate release notes” button. Using GitHub-generated notes gives the action releases the standard structure and compare-based changelog users already expect.
Behavior
The release script now calls
gh release createwith:--generate-notes--notes-start-tag <previous immutable tag>--verify-tagThat keeps the existing tag-creation flow while making the published release notes follow GitHub’s default generated format.