Publish release notes

What this achieves

Release notes are the platform’s record of what changed and when. Customers read the published entries in their own workspace, so this is where that history is written.

Required role: Humavera platform staff.

Steps

Go to Platform → Changelog.
Select Add Entry.
Enter the Version and the Release date.
Enter the Title, and a Description (optional) if a one-line summary helps.
Under Changes, select Add change for each item and describe it, choosing its type.
Leave Published off while you are still writing, or switch it on to release the entry.
Select Add.

Change types

Option	Description
Feature	Something new.
Improvement	Something existing, made better.
Bug Fix	Something that was wrong and is now right.
Security	A security-relevant change.

Example: an entry covering a release might carry two Feature items, three Improvement items, and a Bug Fix, each written as its own line rather than bundled into one paragraph.

Drafts stay internal

An entry with Published off is a draft. Drafts are not shown to customers, and they are marked as drafts in the list here, so an entry can be assembled across a week and released in one move.

Switching Published on makes the entry visible in every customer workspace immediately.

Write each change so a customer can act on it

Each line is read by someone deciding whether it affects them. Name what changed and where, in the words the product uses on screen.

Example: “Payroll reports can now be downloaded as a spreadsheet” tells an administrator something. “Report export improvements” does not.

Deleting an entry cannot be undone.

What happens next

Published entries appear to customers in their own workspace, under their settings, as the running history of the product. An announcement is the right tool for something time-bound like maintenance; release notes are for the record.