yeetpost

Open source releases that reach developers

Turn tags, changelogs, and PRs into release posts across dev channels.

Entityusecase.open_source_releasesIntenthigh

What this is

If you ship OSS but nobody hears about it, adoption lags. yeetpost helps you convert a release into a distribution bundle: a short announcement, a changelog summary, and a “what changed” thread.

When to use it

  • You release frequently and want a consistent “shipping drumbeat”.
  • You want to reuse changelog/release data without rewriting from scratch.

When not to use it

  • Your release notes contain sensitive/customer-specific details.

Common mistakes

  • Only posting a GitHub release link without context.
  • Not highlighting the one change that matters most.

Workflow

  1. On tag/release, fetch notes + key PRs.
  2. Pick a headline change and audience.
  3. Generate variants for X/LinkedIn/Slack/Discord.
  4. Include “how to try it” in every version.

Templates

Release headline + 3 bullets

Write a release post for {channel} from these notes. Start with a headline, then 3 bullets: what, why, how to try. Notes: {notes}

Examples

X (release)

v0.7 shipped.

- Faster webhook delivery
- Better retry semantics
- New “dry run” mode

Try it: {link}

Metrics to track

  • Release post CTR
  • Stars/follows around release
  • Upgrade rate after release

Related use cases