📋 Changelog Manager

Keep your users informed about updates. Auto-generates a beautiful public changelog page.

💡 Why Use a Changelog?

A changelog builds trust with your users by showing you're actively improving your product. It also reduces support tickets — users can see if their feature request was implemented or bug was fixed.

📋 Example Use Case:

You launch a new "Webhook Retry" feature for LaunchQue Pro users. Add it to your changelog:

New: Webhook Retry Logic
Pro users now get automatic webhook retries if the endpoint is temporarily down. Up to 3 attempts with exponential backoff.

Result: Users see you're delivering value, they feel heard, and they're less likely to churn.

📚 Learn More (Best Practices)
  • Be specific: "Fixed email bug" → "Fixed issue where emails weren't sent for forms with special characters"
  • Group by type: New features, Improvements, Bug fixes
  • Update regularly: Weekly or after each deploy
  • Link to docs: Help users understand new features
  • Credit users: "Thanks to @jane for suggesting this!" builds community

📖 Read: How to maintain a good changelog

🌐 Your Public Changelog URL: Loading...
👁️ View Page

⚙️ Settings

➕ Add New Entry

📜 Published Entries

Loading...