Contributor
GitHub Releasesfix(digests): schedule weekly digests in the workspace time zone instead of UTC
Product
ReleaseFlow collects merged work from the tools your team already uses, classifies it with rules anyone can read, asks a person to decide, and publishes a note written for each audience.
Merged pull requests and finished issues from the tools your team already uses.
Rules sort each change into a category and record which rule matched.
A person decides on every change before the release is approved.
A note for each audience, frozen when the release is published.
Walkthrough
Fifty seconds of a real release of a sample project: created, reviewed, approved, published, read without signing in, and posted to Slack.
01 · Collect
GitHub, GitLab, Linear and Jira each describe work their own way. ReleaseFlow records merged pull requests, merged merge requests and completed issues as one kind of change, so review never depends on where the work happened.
Sources

02 · Classify
Classification starts with fixed rules: a Conventional Commit type in the title, a familiar label, or a change that only touches documentation. Each change keeps the rules that matched, so a reviewer can see why it landed where it did.
bug
03 · Review
Release review puts each decision in front of your team: approve a change as shown, correct its classification or summary, or reject it from the release. Then approve the release, check each audience’s note, and publish it.

04 · Publish
When a release is approved, ReleaseFlow writes one note per audience from that audience’s template. Publishing freezes them, and automation rules deliver each note where its readers already are.
fix(digests): schedule weekly digests in the workspace time zone instead of UTC
Digests now follow each workspace’s time zone. Nothing to migrate; watch the first scheduled run.
Scheduled digests now arrive at the time you chose, wherever your team works.

Published notes are frozen: nothing edits them afterwards, not even direct SQL.
Optional providers
ReleaseFlow works without any third-party service. AI, translation, email and delivery run only when you configure them, and the secrets your rules store are encrypted in your own database.
OpenAI, Anthropic or DeepSeek suggest a category, a neutral summary and a narrative for each audience. The rules always win, and words a person wrote are never replaced.
Translate each note into every language your Organization writes in. Publishing waits until every translation is ready.
Send a published note to up to 100 addresses through your own SMTP server.
Post published notes to GitHub Releases, Slack, Microsoft Teams, Notion, Confluence or a Zendesk help centre.
Start ReleaseFlow with Docker Compose, connect one repository, and review your next release before anyone reads it.