Use cases
Releases that go out without a ritual
When the merged work justifies a release, the agent drafts the changelog and cuts the tag on the policy you committed, never holding a token you did not grant it.
The release is the last thing to get automated and the easiest to get wrong
Most teams automate the build and leave the decision, the changelog and the tag to whoever remembers. developerz.ai reads what merged since the last release, drafts the notes from the actual pull requests, and cuts the release when your policy says it is due. Publishing rights stay with your GitHub App installation and your branch protections; there is no separate publish token handed to us, and every release action is an audit entry.
Notes from the merges, not from memory
The changelog is drafted from the pull requests that actually landed, in the window since the previous release.
Your cadence, in the policy file
Per-repo release rules live in maintainer.yml alongside everything else, versioned in the repo like the rest of your config.
Auditable, like everything else
A release is a logged action with an actor and a reason, not an opaque button somebody pressed.
Where it stops and asks you
It cuts the tag; your CI publishes
It never publishes to a package registry: npm, crates, PyPI and RubyGems are refused, because publishing there would mean holding your tokens, so your own CI publishes from the tag it pushes. A repository with no committed maintainer.yml gets no releases at all. One that has tags but none with a stable X.Y.Z version (a leading v is fine) gets none either: nothing runs, and one blocker asks you to tag a baseline or turn releases off, rather than inventing a version. A repository with no tags at all gets its first release. With bump_strategy: bump_pr_first the version bump arrives as a pull request and goes through the same merge gate as any other, pr.human_merge included.
Read the release settingsGo deeper
See what we shipped ourselves
We dogfood this: our own changelog is generated by the same lane, on our own repository.
Read the changelog
Ship more. Maintain less.
We expect software to be written faster than any team can review it. Bring your repos, your boxes and your keys. We bring the org that keeps up.