Skip to content

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

Merged
jdx merged 1 commit intomainfrom
claude/strange-swartz-05db56
Apr 23, 2026
Merged

chore(release): append en.dev sponsor blurb to release notes#231
jdx merged 1 commit intomainfrom
claude/strange-swartz-05db56

Conversation

@jdx
Copy link
Copy Markdown
Contributor

@jdx jdx commented Apr 23, 2026

Summary

  • Appends a Sponsor aube section to every GitHub Release body, run after communique generate in the enhance-release job in .github/workflows/release-plz.yml.
  • The blurb explains that aube is funded by sponsors at en.dev and links to other en.dev projects — consistent with mise#9272.

What it looks like

Rendered at the bottom of each release body:

💚 Sponsor aube

aube is part of en.dev — an independent developer-tooling studio run by @jdx, also behind mise. Work on aube is funded entirely by sponsors.

If aube is saving your team install time or CI minutes, please consider sponsoring at en.dev. Individual and company sponsorships are what keep the project fast, free, and independent.

Test plan

  • `actionlint` + `yamllint` pass on the modified workflow
  • Simulated the heredoc locally to confirm YAML indentation strips cleanly and bash terminates the heredoc correctly
  • 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 enhance-release job to post-process release notes via gh release edit, with no changes to build, publishing, or runtime behavior.

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

This is implemented by fetching the current release notes (gh release view), concatenating a fixed markdown blurb, and updating the release via gh release edit --notes-file.

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

Adds a "Sponsor aube" section at the bottom of each GitHub Release body
after communique generates the narrative notes, so readers landing on a
release see how aube is funded and where to sponsor.

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

greptile-apps Bot commented Apr 23, 2026

Greptile Summary

This PR adds a "Append en.dev sponsor blurb" step at the end of the enhance-release job. It fetches the release body with gh release view, concatenates a heredoc sponsor section, and writes the result back via gh release edit. The heredoc indentation is at the same depth as the surrounding shell commands (10 spaces in YAML), so YAML's block-scalar indentation stripping leaves the markdown lines flush at column 0 — no code-block rendering issue.

Confidence Score: 5/5

Safe to merge — single-step addition with correct heredoc handling and no new security surface.

The change is a small, self-contained step with straightforward logic. YAML indentation stripping is handled correctly, the heredoc terminator reaches column 0 after YAML processing, and the step follows the same token and pattern as adjacent steps. No P0/P1 findings.

No files require special attention.

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, appends a sponsor blurb via heredoc, and writes it back with gh release edit; YAML block-scalar indentation stripping is handled correctly.

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

@jdx jdx merged commit 1ce0e31 into main Apr 23, 2026
16 checks passed
@jdx jdx deleted the claude/strange-swartz-05db56 branch April 23, 2026 16:53
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.

1 participant