Skip to content

fix: avoid duplicating generated notes when updating a release - #844

Open
ump45nose wants to merge 2 commits into
softprops:masterfrom
ump45nose:fix/827-no-duplicate-release-notes
Open

ump45nose wants to merge 2 commits into
softprops:masterfrom
ump45nose:fix/827-no-duplicate-release-notes

Conversation

@ump45nose

Copy link
Copy Markdown

Summary

When updating an existing release with generate_release_notes: true and append_body: false, do not seed the update body from the previous release notes.

prepareReleaseMutation appends freshly generated notes to the body we pass, so reusing the prior body duplicated notes on every re-run.

Changes

  • In src/github.ts, when generate_release_notes && !append_body, use only the workflow body (not the existing release body) as the seed for the update.
  • Add regression coverage in __tests__/github.test.ts.
  • Regenerate dist/index.js.

Fixes #827

Test plan

  • npm run fmtcheck
  • npm run typecheck
  • npm test (vitest: 182 passed)
  • npm run build / dist updated with the change

Notes

AI assistance was used while preparing this change.

ump45nose and others added 2 commits September 27, 2026 07:44
When generate_release_notes is true and append_body is false, do not seed
the update body from the existing release notes. prepareReleaseMutation
appends freshly generated notes to the body we pass, so reusing the prior
body duplicated notes on every re-run.

Fixes softprops#827
Resolve the generated bundle conflict against current upstream dependencies.
Keep README and action input documentation aligned with note regeneration.

AI assistance was used to prepare and validate this change.
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.

[Bug]: generate_release_notes: true duplicates release notes when release already exists on re-run

1 participant