Release posts for X and LinkedIn that read like your team wrote them.
DevRelay drafts the post when a release ships, picks a format that fits the change, checks every claim against the code, and posts to X or LinkedIn when you approve: now, or on the calendar.
Go SDK v2.8.0 adds Stream() for incremental query results.
Stream() returns *Rows backed by a server-side cursor.
Release notes → github.com/fluxdb/go-sdk/releases/tag/v2.8.0
- 11 post formats
- chosen by change kind
- X and LinkedIn
- posts on approval
- Threads
- post as a reply chain
The release shipped. The post is still a to-do.
Nobody decided not to announce it. It just never became anybody's job.
Nobody owns the post
The engineer who shipped it is on the next ticket. The founder means to write it tonight, then the next release lands.
Every post sounds the same
“Excited to announce” on every release. Followers learn to scroll past, and the fix that mattered reads like the feature that didn't.
AI drafts overclaim
A generic writer calls a beta GA, invents a benchmark, or announces a pull request users can't install yet. Once is enough to stop trusting it.
From release to post, with you deciding what goes out.
Six steps. Only the last one needs you.
PR #1832 merged holding
release v2.8.0 released → draftingWaits for the release
HIGH x_post linkedin_post changelog
MEDIUM x_post changelog
LOW changelog
BLOCK held for a humanDecides whether it's worth a post
Picks a format that fits
Checks every claim
Writes in your voice
Posts when you approve
Eleven formats. Picked by what actually changed.
A bug fix shouldn't read like a launch, and a breaking change should never read like a feature. DevRelay picks the formats that fit the change, the writer chooses one, and the last three X formats rotate out so your feed doesn't repeat itself.
- IntroducingThree or more things users can now do. The default for a big release.
- Problem, then fixOpens with the pain the change removes, in the reader's words. Never with an invented statistic.
- How it worksThe capability is a flow (set up, run, result) and the evidence describes its steps.
- MinimalA launch image goes with the post and carries the detail.
- You can nowA new option, flag, method or endpoint. Includes a snippet only if the change has one.
- Before / afterThe evidence shows both the old way and the new way.
- Small winA quality-of-life change with no new API: clearer errors, a faster command.
- Symptom firstA bug fix leads with what users saw, not the internal cause.
- Old → newOnly when the evidence has both numbers and what was measured.
- Heads-upA breaking change or deprecation: what changes, who is affected, the one step to take. Never framed as a feature.
- StoryWhy it matters before how it works. 120 to 220 words, short paragraphs, at most three hashtags at the end.
Approve in the inbox. Plan the week on the calendar.
Approved posts land on the calendar. Drag one to a new time to reschedule; X and LinkedIn posts go out on their own at that time.
Questions about launch posts.
01Does DevRelay post on its own?
No. A person approves the exact version of every post. After approval it goes out immediately or at the time you scheduled. If anyone edits the draft after approval, the approval no longer applies and it needs approving again.
02Can it post X threads?
Yes. A thread is drafted as a series of posts and published as a reply chain from your connected X account. If X rejects a post partway through a thread, DevRelay stops instead of retrying, so you never get a duplicated half-thread.
03Does LinkedIn post to my company page?
It posts as the LinkedIn member who connected the account, which is a personal profile. Company pages aren't supported yet.
04Does it attach images to posts?
Not yet. Posts are text only. For big launches DevRelay drafts a launch image brief built from your brand colours and logo, which you can hand to a designer.
05What stops it from announcing something that isn't released?
The release gate. Merged pull requests are held until a GitHub release includes them, or until they merge into your release branch if the repo is in branch mode. A plain push never counts as a release. Unreleased changes get no post formats at all.
06Which plan do I need?
Drafting, checks and the approval inbox are on the free plan. Posting to X and LinkedIn and scheduling on the calendar need the DevRelay plan.
Your next release, announced the day it ships.
Connect GitHub, X and LinkedIn. The post is waiting for your yes when the release goes out.
No credit card · Nothing posts without your approval