X — 5-post weekly thread
1/ What changed in [Product] this week. [Number] updates, one per post. 2/ [Change 1]: [what it does in one line]. [Screenshot] 3/ [Change 2]: [what it does]. This was requested by [handle or "many of you"]. 4/ [Fixes]: [fix 1], [fix 2], [fix 3]. 5/ Full changelog: [link]. Reply with what you want to see next week.
Bluesky — monthly recap thread
1/ [Product] in [Month]: [number] new features, [number] fixes. Thread below. 2/ The big one: [Feature]. [One-sentence benefit]. 3/ Smaller things: [change], [change], [change]. 4/ Coming next month: [what you are working on, without dates you cannot keep]. 5/ Changelog: [link]
Mastodon — single post with sections
[Product] changelog, week of [date] Added - [item] - [item] Changed - [item] Fixed - [item] - [item] Details: [link] #[ProductTag] #Changelog
X — single post teaser
[Number] changes shipped in [Product] this [week/month]. The one most people will notice: [change]. The rest are in the thread below.
Tips
- Post the thread on the same weekday each cycle. Consistency turns a changelog into something people look for.
- Keep one change per post in the thread so replies attach to a specific item.
- Use the Added, Changed, Fixed grouping from the Keep a Changelog convention; developers recognize it instantly.
- Attach a screenshot to the post for the most visual change, with alt text, and leave the rest text-only.
Frequently asked questions
How long can each post in a changelog thread be?
Each post on X is limited to 280 weighted characters, each Bluesky post to 300 characters, and Mastodon posts to 500 by default. A thread splitter or per-network length check catches overruns before you publish.
Can an agent assemble the changelog thread for me?
Yes. An agent can gather merged changes, fill this template, and submit it as a draft thread in SocialHandoff; a person reviews it in the approval inbox and it publishes as a proper reply chain.