HyperRelease Public Changelogs

Publish a public changelog for your users directly from HyperRelease — without additional development.

Your users want to know what changes with every version. A well-maintained public changelog builds trust and reduces support questions. HyperRelease lets you publish that changelog without building a custom page.

A ready-to-use page

Every HyperRelease project can expose a public changelog page. Published releases appear there with their release notes, accessible via a dedicated URL you share with your community.

Linked to your release process

The public changelog is not a separate document. It draws from the work you already do in the release workspace. When a version moves to Published, your users can see what changed.

Simplified product communication

Marketing and support have a stable link to version history. No more "what changed in 2.3?" with no answer — everything is documented in one place.

In summary

A public changelog is a detail that matters for product credibility. HyperRelease makes it accessible without a dedicated engineering project.

Read more

Public changelog page

HyperRelease documentation

Next article

Manage App Store and Play Store Locales

HyperRelease connects your project locales to App Store and Play Store requirements for multilingual releases without confusion.

We value your privacy

HyperRelease uses essential cookies and local storage to keep you signed in, monitor errors, and remember your preferences. With your consent, we also use OpenPanel analytics to understand product usage, and DataFast analytics cookies when you accept them. Optional marketing cookies are off until you choose otherwise. You can change your choice at any time from Cookie settings in the footer or your account settings.