Your git log already has this week's update. We publish it as a changelog feed, so people who would use or contribute can see the project is alive.
How it works
Name the project and point us at the repo. We watch the commits and draft the issue you would have written. Your host, your license, your code. We only publish the story.
The feed
Each card is a changelog issue, written from commits. Filter by kind, open a profile, or keep scrolling.
A quieter week on hardware, a louder week on the app. The button-clicker now holds instead of tapping.
A page that did not change no longer gets rewritten. The manifest now records why a file was skipped.
If the tarball moved, the install stops. cask diff no longer reprints the whole file for one pin.
That is the whole feed.
Readers
Each issue lands on a public project page. People subscribe once and get every later issue. A launch day is a pulse. A feed is the flywheel.
Pricing
Free is a real project page and posts you write yourself. Paid is automation: weekly, monthly or quarterly. Annual billing is about two months free.
$0 forever
A public project page, a profile, and posts you write by hand. Listed in the directory.
$5 /mo, billed annually
Four automated issues a year. For repos that move slowly but should still look alive.
$12 /mo
The default. A monthly automated issue plus email to subscribers. Annual is $120.
$29 /mo
For repos that ship every week. Priority processing, multiple repos, and a custom domain.
You can, and most maintainers will not. Writing about the work competes with doing the work and loses. We remove the writing, not the publishing.
The moment you want users or contributors, you are doing distribution, in hours or in money. A monthly changelog written by hand costs one to three hours. $12 buys those hours back. The code stays under your license.
A personal blog starts at zero every time. Here the issue lives in a directory of open source projects, and subscribers stay on the project page. Each later issue reaches them without another launch post.
Open source is a license, not a vow of silence. You are paying for communication tooling, the same category as CI or a domain. We never touch the repo or the license.
Pause the plan. The project page and subscribers stay. A weekly plan on a quiet repo should downshift, not publish thin issues.
Register a repo. The first draft is built from your commits. You keep building. The feed keeps showing up.