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

[jdx]

Summary

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

What it looks like

Rendered at the bottom of each release body:

💚 Sponsor usage

usage is built by @jdx at en.dev — an independent developer-tooling studio behind mise, aube, hk, and more. Work on usage is funded by sponsorships.

If `usage` powers CLI specs, docs, or completions for a tool you maintain or use, please consider sponsoring at en.dev. Every sponsorship helps the project stay independent and moving.

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: only adjusts the GitHub Actions release workflow to post-process release notes; no runtime or security-sensitive application code changes.

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

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

^{Reviewed by Cursor Bugbot for commit d1de688. Bugbot is set up for automated code reviews on this repo. Configure here.}

[gemini-code-assist]

Note

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

[greptile-apps]

Greptile Summary

This PR adds a post-release step to the enhance-release job that fetches the just-updated release body (after communique generate), appends a sponsor blurb via a bash group-redirect + heredoc, and writes it back with gh release edit. The implementation mirrors the same pattern used in mise#9272 and is logically sound — YAML block-scalar indentation is correctly stripped so the heredoc delimiter and Markdown headings land at column 0 in the executed script, and the job's sequential steps keep it idempotent across retries.

Confidence Score: 5/5

Safe to merge — single workflow step with no logic bugs or security concerns.

All changes are confined to a single CI workflow step. The heredoc/YAML indentation interaction is correct, the GH_TOKEN env var is properly set, $TAG is safely quoted, and the job ordering ensures the release exists before the step runs. No P0 or P1 findings.

No files require special attention.

Important Files Changed

Filename	Overview
.github/workflows/publish-cli.yml	Adds a new step in the enhance-release job that fetches the current release body, appends a sponsor blurb via heredoc, and writes it back with gh release edit; logic is correct and idempotent.

Sequence Diagram

sequenceDiagram
    participant GHA as GitHub Actions
    participant communique as communique CLI
    participant GH as GitHub Releases API

    GHA->>communique: communique generate "$TAG" --github-release
    communique->>GH: gh release edit (AI-generated notes)
    GHA->>GH: gh release view "$TAG" --json body --jq .body
    GH-->>GHA: current release body
    Note over GHA: Append sponsor blurb via heredoc → /tmp/release-notes.md
    GHA->>GH: gh release edit "$TAG" --notes-file /tmp/release-notes.md

Loading

_{Reviews (1): Last reviewed commit: "chore(release): append en.dev sponsor bl..." | Re-trigger Greptile}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.03%. Comparing base (06510f4) to head (d1de688).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #598   +/-   ##
=======================================
  Coverage   79.03%   79.03%           
=======================================
  Files          48       48           
  Lines        7235     7235           
  Branches     7235     7235           
=======================================
  Hits         5718     5718           
  Misses       1140     1140           
  Partials      377      377           

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.