Release Notes

Release notes are how you tell your community what you've shipped. PathPro's release notes system lets you document every version, link completed tasks and features, and automatically notify the people who care most -- turning every release into a moment of engagement.

Creating Release Notes

To create a release note, navigate to the Release Notes section of your project and click "New Release". Each release note is built around a few key fields:

• Version Number -- A label for this release (e.g., "v2.4.0," "January 2026 Update," or any naming convention your team uses). This becomes the heading that your community sees.
• Description -- A rich-text area where you describe what's included in this release. You can write high-level summaries, detailed changelogs, or anything in between. The description supports formatting, links, and inline images.

There's no enforced format for release notes, so you can adapt them to your communication style. Some teams write brief bullet points listing what changed. Others write narrative descriptions explaining why changes were made and how they benefit users. The flexibility is yours.

Each release note is timestamped with its creation date, and you can edit the content at any time after creation. If you catch a typo or want to add more context after publishing, just open the release note and update it.

Linking Tasks and Features

One of the most powerful aspects of PathPro's release notes is the ability to link them directly to the tasks and features that were completed in that release. When creating or editing a release note, you can search for and attach any tasks from your roadmap.

Linking tasks to a release note creates a traceable line from the work your team did to the announcement your community reads. This connection serves multiple purposes:

• For your community -- Linked tasks show up as a list within the release note, so readers can click through to see the full details of each completed item. This is especially meaningful for features that were originally community-voted, because voters can see their request going from idea to shipped product.
• For your team -- Linking tasks ensures nothing falls through the cracks. When you're composing release notes, the task list serves as a checklist of everything that was completed. If a task isn't linked, it might be missing from the announcement.

You can also link features from the voting board to release notes. When a community-requested feature ships and appears in a release note, the feedback loop is fully closed -- the person who submitted the idea can see it acknowledged, confirmed, built, and shipped.

Author Attribution

Every release note in PathPro includes author attribution, showing which team member published the release. The author's name and avatar appear at the top of the release note, giving the announcement a personal touch.

Author attribution helps humanize your product team. Instead of releases appearing from a faceless company, your community sees the actual people behind the work. This builds a stronger connection between your team and your users.

If multiple team members contributed to a release, the primary author (the person who created the release note) is displayed. Your team can coordinate internally to decide who publishes each release -- some teams rotate the responsibility, while others assign it to a product manager or community lead.

Published vs Draft

Release notes support a two-stage workflow with Draft and Published states, giving your team the ability to prepare announcements before sharing them with the community.

Draft release notes are only visible to team members (Admins and Team Members). This lets you compose the release note, link tasks, review the content with your team, and make edits -- all without your community seeing a work-in-progress announcement. Drafts are ideal when you want to coordinate the timing of an announcement or when multiple team members need to review the content before it goes live.

Published release notes are visible to everyone who can access your project. Once you publish, the release note appears on your public changelog, and any configured email notifications are triggered. Publishing is a one-click action from the draft state.

You can revert a published release note back to draft if needed, though be aware that community members who already saw the notification won't "unsee" it. The revert is useful for correcting errors or temporarily hiding a release note while you update it.

Public Changelog View

Your community accesses release notes through the public changelog page, which is a dedicated section of your project's public-facing site. The changelog displays all published release notes in reverse chronological order -- newest first -- using an accordion format.

Each entry shows the version number, publication date, and author. Clicking on an entry expands it to reveal the full description and any linked tasks. This accordion design keeps the page clean and scannable, even if you have dozens or hundreds of release notes. Community members can expand only the entries they're interested in.

The changelog page supports infinite scroll, so there's no pagination to deal with. As your community scrolls down, older release notes load automatically. This makes it easy for someone who's been away for a while to catch up on everything they missed by simply scrolling through the timeline.

The changelog is a powerful trust-building tool. When prospective users visit your project, a well-maintained changelog demonstrates that your product is actively developed and that your team communicates regularly. It's one of the first places savvy evaluators look when considering a new tool.

Email Notifications

When you publish a release note, PathPro can automatically send email notifications to your community members who have opted in to receive updates. This ensures that your biggest supporters -- the people who registered and chose to stay informed -- hear about new releases immediately.

Email notifications include the version number, a summary of the release, and a link to the full release note on your project's changelog. Recipients can click through to read the details, see linked tasks, and explore what's new.

The notification system respects user preferences. Community members can opt in or out of release note emails from their profile settings, and your project settings control whether notifications are enabled at the project level. This prevents unwanted emails while ensuring that engaged users stay in the loop.