Release announcement generator

What happens to your text

Your notes are sent to an AI model to write the drafts, and are not stored by upTake. Do not paste anything confidential. The drafts are written by AI: read them before posting, and correct anything that is not exactly what you shipped.

In an upTake project, this is done for each GitHub release, with a tagged link per channel so the announcement itself is measured. See what upTake reads from GitHub.

What makes an announcement work

Lead with what changes for the user. “Export 50 invoices in one click” beats “New: batch export”. The version number can wait for the changelog.

One change per post. A list of six fixes is a changelog. Pick the one people asked for and give it the post.

Show it. A screenshot or a ten-second clip says more than a paragraph, on every platform.

Tag the link. Give each platform its own tagged link, so you know which announcement brought the signups. The link builder writes them.

One draft per place

X rewards a short, concrete line and a visual. LinkedIn reads better as a small story: the problem, what you built, what it changes. The changelog is the factual record: what changed, in plain words, with the date. That is why the generator writes three different texts rather than one.

From this tool to your own project

Review the generated drafts before posting. In your own project, GitHub changes can become posts in Write, with a tracked link per network. Sending or scheduling needs a supported, available connection.

Enlarge screenshot ↗