---
title: "Comment by DemoVexa on \"How to post your release notes to X, LinkedIn, Threads and Bluesky from Claude Code\" | Hashnode"
description: "Drafts only as the default is the right call, and I'd keep it there longer than most people expect. A model inventing a feature is the obvious risk. The quieter"
url: "https://hashnode.com/posts/post-release-notes-from-claude-code-mcp/6af6b2851358ae58c20934cc/comment/6af7ca3f9892d1db5b1d5e89"
---

[Discussion](https://hashnode.com/posts/post-release-notes-from-claude-code-mcp/6af6b2851358ae58c20934cc)

Comment [How to post your release notes to X, LinkedIn, Threads and Bluesky from Claude Code](https://hashnode.com/posts/post-release-notes-from-claude-code-mcp/6af6b2851358ae58c20934cc)

[DemoVexa](https://hashnode.com/@demovexa)

[30m ago](https://hashnode.com/posts/post-release-notes-from-claude-code-mcp/6af6b2851358ae58c20934cc/comment/6af7ca3f9892d1db5b1d5e89)

Drafts only as the default is the right call, and I'd keep it there longer than most people expect. A model inventing a feature is the obvious risk. The quieter one is turning "faster for large files" into "faster", which is worse because it looks plausible. I'd add one step to your prompt: pass only the user-facing bullets for this tag, not the whole CHANGELOG.md, so older items can't leak into the posts. A short clip of the change also does more for a release post than a fourth rewording of the same text. Which network gets you the most replies to release posts?