Skip to content

chore(release): append en.dev sponsor blurb to release notes#106

Merged
jdx merged 2 commits intomainfrom
claude/sponsor-blurb-release-notes
Apr 23, 2026
Merged

chore(release): append en.dev sponsor blurb to release notes#106
jdx merged 2 commits intomainfrom
claude/sponsor-blurb-release-notes

Conversation

@jdx
Copy link
Copy Markdown
Owner

@jdx jdx commented Apr 23, 2026 •
edited by cursor Bot
Loading

Summary

  • Appends a Sponsor communique section to every GitHub Release body, run after communique generate in the enhance-release job in .github/workflows/release-plz.yml.
  • Same pattern as mise#9272, adapted for communique.

What it looks like

Rendered at the bottom of each release body:

💚 Sponsor communique

communique is developed by @jdx at en.dev, an independent studio behind developer tools like mise, aube, hk, and more. Ongoing work on communique is funded by sponsorships.

If communique is drafting your release notes or changelogs, please consider sponsoring at en.dev. Every sponsor — individual or company — helps keep the project independent and actively maintained.

Test plan

  • `actionlint` + `yamllint` pass on the modified workflow
  • Next tagged release produces a GitHub Release whose body ends with the sponsor section

🤖 Generated with Claude Code

Note

Low Risk
Low risk: CI/workflow-only change that edits GitHub Release text after generation; main risk is accidental overwriting/formatting of release notes if the gh step fails or output changes.

Overview
After communique generate runs in the enhance-release workflow, the job now appends a “Sponsor communique” section to the existing GitHub Release body.

This is implemented by fetching the current release notes via gh release view, concatenating the sponsor blurb, and updating the release via gh release edit --notes-file.

Reviewed by Cursor Bugbot for commit 432e7eb. Bugbot is set up for automated code reviews on this repo. Configure here.

@jdx @claude
chore(release): append en.dev sponsor blurb to release notes
ab79012 
Adds a "Sponsor communique" section at the bottom of each GitHub Release
body after communique generates its own narrative notes, so readers who
land on a release see how communique is funded and where to sponsor.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
@gemini-code-assist
Copy link
Copy Markdown

gemini-code-assist Bot commented Apr 23, 2026

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Apr 23, 2026 •
edited
Loading

Greptile Summary

Adds a new step to the enhance-release job that fetches the published GitHub release body and appends a static sponsor blurb via gh release edit. The heredoc indentation is handled correctly by YAML's block-scalar stripping, so the rendered Markdown will be clean.

Confidence Score: 5/5

Safe to merge; only a minor idempotency gap on manual re-runs, no data-loss risk.

The change is small and low-risk. The single finding (no duplicate-blurb guard) is P2 — it only triggers on manual job re-runs, not normal release flow, and the worst outcome is a duplicate section rather than data loss or a broken release.

No files require special attention beyond the idempotency note in .github/workflows/release-plz.yml.

Important Files Changed

Filename Overview
.github/workflows/release-plz.yml Adds a new step to the enhance-release job that fetches the current release body and appends a static sponsor blurb via gh release edit; no idempotency guard means re-runs will duplicate the section.

Sequence Diagram

sequenceDiagram
    participant RLP as release-plz-release
    participant UP as upload-assets
    participant PR as publish-release
    participant ER as enhance-release

    RLP->>RLP: release-plz creates tag + draft release
    RLP->>UP: tag output
    UP->>UP: build & upload binaries
    UP->>PR: done
    PR->>PR: gh release edit --draft=false (publishes)
    PR->>ER: done
    ER->>ER: cargo build + communique generate (updates body)
    ER->>GitHub: gh release view (fetch current body)
    GitHub-->>ER: release body markdown
    ER->>ER: cat body + heredoc blurb → /tmp/release-notes.md
    ER->>GitHub: gh release edit --notes-file (append sponsor blurb)
Loading

Fix All in Claude Code

Reviews (2): Last reviewed commit: "Merge branch 'main' into claude/sponsor-..." | Re-trigger Greptile

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 23, 2026 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.08%. Comparing base (536b3d5) to head (432e7eb).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files 
@@           Coverage Diff           @@
##             main     #106   +/-   ##
=======================================
  Coverage   94.08%   94.08%           
=======================================
  Files          26       26           
  Lines        4055     4055           
  Branches     4055     4055           
=======================================
  Hits         3815     3815           
  Misses        155      155           
  Partials       85       85

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@jdx jdx enabled auto-merge (squash) April 23, 2026 16:52
@jdx jdx merged commit 1585680 into main Apr 23, 2026
7 checks passed
@jdx jdx deleted the claude/sponsor-blurb-release-notes branch April 23, 2026 16:54
@jdx jdx mentioned this pull request Apr 23, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jdx