Release Announcement Generation Prompt

You are a technical content writer creating a release announcement for version  of .

### Context
- **Release Version:** 
- **Release Date:** 
- **Release Type:** 
- **Target Audience:** 
- **Tone:** 
- **Output Format:** 

### Changelog Content


### Instructions

Create a compelling release announcement that includes:

1. **Headline**
   - Catchy, descriptive title that highlights the main value proposition
   - Should be under 100 characters for social media compatibility
   - Examples:
     - " : Faster, Stronger, Better"
     - "Introducing   with "
     - "  – "

2. **Opening Paragraph**
   - Brief, engaging introduction (2-3 sentences)
   - State what's new and why it matters
   - Hook the reader to continue

3. **Key Features Section**
   - Highlight 3-5 most important changes
   - Focus on benefits, not just features
   - Use bullet points for scannability
   - Include code examples for technical features (if applicable)

4. **Breaking Changes** (if applicable)
   - Clear warning about breaking changes
   - Brief migration guidance or link to full guide
   - Estimated upgrade effort

5. **Migration Notes** (if breaking changes)
   - Step-by-step upgrade instructions
   - Common pitfalls to avoid
   - Support resources

6. **Performance Metrics** (if applicable)
   - Quantify improvements with numbers
   - Use comparisons (e.g., "40% faster than v1.1.0")
   - Include benchmarks or charts

7. **Community Recognition**
   - Thank contributors by name (if available)
   - Highlight first-time contributors
   - Link to contributor profiles

8. **What's Next**
   - Tease upcoming features
   - Link to roadmap or project board
   - Invite community feedback

9. **Call to Action**
   - Clear next steps (download, upgrade, try it)
   - Links to documentation, changelog, GitHub release
   - Support channels for questions

### Style Guidelines

- Use active voice
- Write conversationally but professionally
- Explain technical concepts clearly for 
- Keep paragraphs short (2-4 sentences)
- Use headings and bullet points for structure
- Include relevant links and resources
- Proofread for grammar and clarity

### Special Instructions for 


- Target length: 800-1200 words
- Include table of contents
- Add relevant images/screenshots (describe where needed)
- SEO-friendly meta description (160 characters)
- Include code examples with syntax highlighting
- Add "Related Posts" section at end



Generate variants for:
- **Twitter/X:** Under 280 characters, include hashtags
- **LinkedIn:** 1-3 paragraphs, professional tone
- **Mastodon:** Under 500 characters, technical community focus
- **Bluesky:** Under 300 characters, casual but informative

Include:
- Emoji use (sparingly, 1-2 per post)
- Relevant hashtags (# #release #opensource)
- Visual assets needed (screenshot, banner, demo GIF)



- Subject line variants (3 options, A/B test ready)
- Preheader text (preview text, ~100 characters)
- Mobile-friendly formatting
- Clear CTA buttons
- Footer with links to: documentation, GitHub, support, unsubscribe



- Use GitHub-flavored Markdown
- Link to related issues and PRs
- Include checkboxes for user feedback
- Tag relevant users/teams
- Enable reactions for quick feedback
- Pin important notices


### Output Format

Provide the announcement in clean Markdown format, ready to publish.
Include all sections outlined above.
Add YAML frontmatter if the format requires it.

   is live!






📖 Changelog: 
⬇️ Download: 

# #release #opensource

I'm excited to announce the release of  ! 🎉



Key highlights:
• 
• 
• 



This release wouldn't be possible without our amazing contributors. Thank you to everyone who reported issues, submitted PRs, and participated in discussions.

Learn more and download: 

# #OpenSource #SoftwareDevelopment #

  released! 🚀








Full changelog: 
Docs: 

# #opensource # #release

  drops today! 



New: 

Get it: