Loading...
×Use Claude Code with Tareno to turn release notes and the diff into a Bluesky thread: headline change, breaking changes, upgrade command. Saved as one draft you approve in Tareno.
Yes. Claude Code reads the release notes and the diff, finds breaking changes the notes missed, writes a thread with a headline post, one post per breaking change and an upgrade post, and saves the whole thread as one draft through Tareno. Scheduling stays pending until you approve it in Tareno.
Last reviewed 2026-10-24 · Markdown version for AI agents
A release that breaks something deserves more than one post, and the people who are about to be broken want to see exactly what changes for them. On a network that stores one post at a time, that means a link and a hope. On Bluesky, Tareno saves a whole thread as one draft, so a maintainer can put the headline in the root post, each breaking change in its own reply and the upgrade command at the end. Claude Code adds the part that makes the thread trustworthy: it reads the diff and finds the breaking change the notes forgot. This page follows a library maintainer through a major release.
Imagine a maintainer releasing version 3.0 of a date library. She asks Claude Code to read the release notes and the diff against 2.9. The notes list one breaking change, a renamed function. Claude Code finds a second in the diff: a default time zone changed from local to UTC, which the notes do not mention. It proposes a thread of five posts: the headline, the rename, the time zone change, the upgrade command, which it ran in a scratch project, and a link to the migration guide. It saves the thread as one draft with create_drafts, and she corrects the notes too.
Point Claude Code at the previous tag and the new one. Reading the diff, not only the notes, is how it finds breaking changes that the notes miss.
Ask for a table of changes to public functions, defaults and removed options, each with the file it is in. Compare it with the notes and fix the notes first.
Ask Claude Code to run the upgrade or install command in a scratch project and report the output. A command in a thread gets copied.
Request a thread with the headline in the root, one reply per breaking change and a last reply with the command and the migration link. Each post stays within 300 characters.
Claude Code confirms the account with list_accounts and saves the root and the replies through create_drafts in a single call. Read the draft top to bottom in Tareno.
Give a day, a time and an IANA time zone. The request becomes a pending action, and you approve it in the Tareno dashboard.
Compare tags [v2.9.0] and [v3.0.0] and list every change to public functions, default values and removed options as a table with the file and the line. Then compare the table with the release notes and name every breaking change the notes do not mention.In a clean scratch project, install the old version, run the example from the README, then run the documented upgrade command [command] and the example again. Show me the output of both runs and tell me whether the README example still works.Write a Bluesky release thread for Tareno: a root post with the headline, one reply for each breaking change from the table, and a final reply with the upgrade command and the migration link. Every post must stay within 300 characters and make sense alone. Give me the count of each.Use Tareno to confirm the Bluesky account [project handle] and save the approved root post and replies as one thread draft. Return the draft ID and the number of replies, and request no time until I give you the day and the time zone.As configured in Tareno on 2026-10-24. The live rules for your own account come from the get_platform_schema tool.
Source: AT Protocol lexicons: app.bsky.feed.post and app.bsky.embed, read on 2026-10-25. Platform rules change; check the page before you rely on a number.
https://tareno.co/api/mcpUse the same Tareno account across supported clients. Open the relevant setup guide for authentication, first use, reconnect, and revocation.
list_accountsChecked:
Because each breaking change needs its own sentence, and people look for the one that affects them. A Bluesky thread in Tareno lets the root carry the headline and each reply one change, saved as a single draft.
By comparing the public surface between two tags: function signatures, defaults and removed options. It reports differences the notes do not mention. It cannot see how users call your code, so it states changes, not consequences.
Yes, as plain text in a reply. Bluesky has no code formatting in Tareno's configuration, so keep the command to one line, and have Claude Code run it in a scratch project before it goes into the thread.
Tareno cannot add a reply to a published thread. Publish a short correction as a new post, and ask Claude Code to compare the new change with the rest of the diff before you do.
Up to 24 replies after the root, each within 300 characters. A release thread rarely needs more than six posts, and a shorter thread gets read to the end more often.
No. A scheduling request becomes a pending action in Tareno, and Bluesky receives the thread only after you approve it in the dashboard. `get_action_status` shows what happened afterwards.