Use release-please body output instead of CHANGELOG.md in release workflow #6
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.
The release workflow was referencing the entire
CHANGELOG.mdfile for GitHub release bodies, making releases verbose with all historical changes instead of version-specific notes.Changes
bodyoutput from release-please step to bump job outputsbodyparameter instead ofbody_path: CHANGELOG.mdgenerate_release_notes: true(redundant with release-please body)outputs: release_created: ${{ steps.release.outputs.release_created }} tag_name: ${{ steps.release.outputs.tag_name }} + body: ${{ steps.release.outputs.body }}- name: GitHub Release uses: softprops/action-gh-release@v2 with: tag_name: ${{ needs.bump.outputs.tag_name }} - generate_release_notes: true - body_path: CHANGELOG.md + body: ${{ needs.bump.outputs.body }} prerelease: ${{ github.event.inputs.release-type == 'next' }}Releases now contain only the relevant version's notes as generated by release-please.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.