fix(release): avoid duplicate sponsor blurbs#488
Conversation
Greptile SummaryThis PR makes the sponsor-blurb append step idempotent by caching the release body in Confidence Score: 5/5Safe to merge — minimal, correct change to a single workflow step with no logic regressions. The idempotency guard is logically correct: YAML indentation stripping ensures the heredoc emits No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "fix(release): avoid duplicate sponsor bl..." | Re-trigger Greptile |
Benchmark changesVersions:
Public ratios: warm installs vs Bun 7x -> 4x; warm installs vs pnpm 11x -> 9x.
ae3bf33 vs b3ec965 | aube/bun/pnpm | 3 scenarios | 3 runs | 500mbit/50ms | generated by Codex. |
Summary
Testing
actionlint .github/workflows/release-plz.ymlgit diff --checkThis PR was generated by Codex.
Note
Low Risk
Low risk workflow-only change that makes release-note editing idempotent by detecting an existing sponsor section before appending.
Overview
Makes the
enhance-releaseworkflow’s “Append en.dev sponsor blurb” step idempotent by fetching the current GitHub release body once, checking for the existing## 💚 Sponsor aubeheader, and skipping the edit when it’s already present.When absent, it reuses the fetched body and appends the sponsor section as before, preventing duplicate blurbs across reruns.
Reviewed by Cursor Bugbot for commit ae3bf33. Bugbot is set up for automated code reviews on this repo. Configure here.