Skip to content

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

Merged
jdx merged 1 commit intomainfrom
claude/sponsor-blurb-release-notes
Apr 23, 2026
Merged

chore(release): append en.dev sponsor blurb to release notes#372
jdx merged 1 commit intomainfrom
claude/sponsor-blurb-release-notes

Conversation

@jdx
Copy link
Copy Markdown
Collaborator

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

Summary

  • Appends a Sponsor pitchfork 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 pitchfork.

What it looks like

Rendered at the bottom of each release body:

💚 Sponsor pitchfork

pitchfork is built by @jdx at en.dev — an independent studio shipping developer tools like mise, aube, hk, pitchfork, and more. Development is sustained by sponsorships.

If pitchfork has a place in your dev workflow, please consider sponsoring at en.dev. Individual and company sponsorships are what keep the project healthy and moving forward.

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 workflow-only change that edits GitHub Release bodies via gh release edit; main risk is malformed/duplicated release notes if the script or gh call fails.

Overview
After communique generate in the enhance-release job, the workflow now fetches the current release body for the new tag and re-edits the GitHub Release to append a “Sponsor pitchfork” section with en.dev sponsorship links.

Reviewed by Cursor Bugbot for commit 03c5d49. 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
03c5d49 
Adds a "Sponsor pitchfork" section at the bottom of each GitHub Release
body after communique generates the narrative notes, so readers who
land on a release see how pitchfork is funded and where to sponsor.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@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
Contributor

greptile-apps Bot commented Apr 23, 2026

Greptile Summary

This PR adds a new step to the enhance-release job in the release workflow that appends a sponsor blurb to every GitHub Release body. The step reads the current release notes via gh release view, concatenates the sponsor section via a heredoc, and writes back with gh release edit.

Confidence Score: 5/5

Safe to merge — simple workflow step with correct error handling and proper guards already in place.

The change is a single new shell step inside an already-guarded job. Default -eo pipefail shell ensures the edit command is never reached on a failed read, the heredoc indentation resolves correctly after YAML stripping, and no new secrets or permissions are introduced. No P0/P1 findings.

No files require special attention.

Important Files Changed

Filename Overview
.github/workflows/release-plz.yml New step appends sponsor blurb after communique generates release notes; correct YAML heredoc indentation, protected by existing job-level tag guard, default -eo pipefail shell prevents partial writes on error.

Sequence Diagram

sequenceDiagram
    participant RP as release-plz-release
    participant UA as upload-assets
    participant ER as enhance-release

    RP->>RP: run release-plz (creates tag + GH Release)
    RP-->>UA: outputs.tag
    UA->>UA: upload binary assets
    UA-->>ER: done
    RP-->>ER: outputs.tag
    ER->>ER: communique generate (AI-enhanced notes)
    ER->>GitHub: gh release view --json body
    GitHub-->>ER: current release body
    ER->>ER: append sponsor heredoc → /tmp/release-notes.md
    ER->>GitHub: gh release edit --notes-file /tmp/release-notes.md
Loading

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

@jdx jdx merged commit f865f8e into main Apr 23, 2026
6 checks passed
@jdx jdx deleted the claude/sponsor-blurb-release-notes branch April 23, 2026 16:52
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