fix: Release PRs no longer include old changelog entries after publishing

Merged
HA
6mo ago
+78-3

Summary

  • Prevent release-please from opening a new release PR from a release commit before the native publisher has finished creating the GitHub release.
  • Keep generated release PRs scoped to the actual changes since the latest published release.

User Impact

  • A merged release PR no longer immediately creates a follow-up release PR with historical changelog entries.
  • Maintainers can close the oversized beta.5 release PR and continue from the next real change.

Changes

  • Detect release-please release commit subjects before running the release workflow body.
  • Skip release-please and release PR binary sync when the push is only a release commit.
  • Add a shell helper test so scoped beta release commits and normal commits are handled separately.

Verification

  • scripts/test-resolve-native-cli-release-target.sh
  • scripts/test-is-release-please-release-commit.sh
  • scripts/test-mark-release-pr-tagged.sh
  • scripts/test-sync-published-release-pr-labels.sh
  • scripts/test-sync-release-please-go-cli-dist.sh
  • scripts/test-notify-release-workflow-failure.sh
  • scripts/test-install-release-filter.sh