Purpose
The Release notes page is a read-only record of what has changed on the platform. Each release lists the new features, fixes, and improvements that went live, when they were deployed, and which parts of the system they touched. Use it to check whether a change you were expecting has shipped, to confirm a deployment went out, or to understand what a recent update did. Open it from the dashboard sidebar, or go directly to/dashboard/changelog.
This page is read-only. There are no buttons to edit, add, or delete entries, and there are no fields to fill in. You are only ever viewing what has already been published.
How the page is laid out
Releases appear as a timeline, newest first. Each release is a card you can read top to bottom. Inside a card you see a summary of the whole release, then the individual changes that make it up.Reading a release card
The top of each card describes the release as a whole.| Detail | What it tells you |
|---|---|
| Version | The release’s version number, shown as a semantic version such as v1.2.3. Higher numbers are newer. |
| Title | A short name for the release. |
| Release date | The date and time the release was published. |
| Deployment status | A badge showing whether the release is live. See Deployment status below. |
| Summary | A short plain-language description of what the release is about. |
| Components updated | Coloured tags naming which parts of the system were changed in this release. See Component tags. |
Deployment status
The status badge at the top of each card tells you whether the release actually reached the live system.| Badge | Colour | Meaning |
|---|---|---|
| Deployed | Green | The release is live and running. |
| Pending | Blue | The release is prepared but not yet live. |
| Rollback | Red | The release was reversed after going out. Treat its changes as no longer active. |
Component tags
The Components updated tags show which parts of the platform a release changed. They are colour-coded so you can scan them quickly. These are the internal names of the call engine, the back-end service, and the console interface — you do not need to act on them, they are there to show the scope of a release.Reading an entry
Inside each release card, every individual change is shown as its own entry. An entry is the most detailed level — it explains one specific change.| Part of the entry | What it shows |
|---|---|
| Type | A badge classifying the change (feature, fix, and so on). See Entry type. |
| Impact | A badge showing how significant the change is. See Entry impact. |
| Component | The specific part of the system the change applies to, shown inline with its own colour. |
| Title | A short heading describing the change. |
| Description | A fuller explanation of what changed and why. |
| Technical details | An optional, more technical explanation. Only appears when there is extra detail to share. |
| Metrics | Optional before-and-after performance numbers with the improvement shown as a percentage. Only appears for changes that were measured. |
| Affected calls | An optional list of the specific calls a change touched. Each call is shown by the first few characters of its ID followed by ... (for example abc12345...). |
Entry type
The type badge tells you what kind of change an entry is.| Type | Colour | What it means |
|---|---|---|
| Feature | Blue | Something new was added. |
| Bugfix | Red | A problem was corrected. |
| Performance | Green | Something was made faster or lighter. |
| Security | Blue | A security-related change. |
| Operational | Grey | A behind-the-scenes or maintenance change. |
Entry impact
The impact badge tells you how significant a change is, which helps you decide how closely to read it.| Impact | Colour | What it means |
|---|---|---|
| Critical | Red | A major change worth paying close attention to. |
| High | Blue | An important change. |
| Medium | Blue | A moderate change. |
| Low | Green | A minor change. |
Metrics
When a change was measured, the entry shows a Metrics section with the before and after numbers (in milliseconds) and the improvement as a percentage. This is how you can see, for example, that a response time dropped from one value to another and by how much. If no measurement was recorded, this section does not appear.Affected calls
Some entries — usually fixes — list the specific calls that were affected by an issue or its correction. Each call is shown by a shortened ID (the first few characters followed by...). The list is limited to the first several calls and is there for traceability, not as a full audit. To see a call in full, look it up on the call pages. See Call detail.
Empty and loading states
| Situation | What you see |
|---|---|
| No releases yet | A large branch icon with the heading “No Release Notes Yet” and the text “Release notes will appear here once you start adding changelog entries.” |
| Page still loading | Placeholder skeletons in the shape of the header and the first few release cards, shown while the entries load. |
Quick reference
Is a change live?
Is a change live?
Check the Deployment status badge on the release card. Deployed (green) means it is live, Pending (blue) means it has not gone out yet, and Rollback (red) means it was taken back and is no longer active.
How significant is a change?
How significant is a change?
Look at the Impact badge on the entry: Critical (red) is the most significant, then High and Medium (blue), then Low (green). The Type badge tells you whether it is a new feature, a fix, a performance change, a security change, or an operational one.
What do the coloured component tags mean?
What do the coloured component tags mean?
Can I edit or remove a release note?
Can I edit or remove a release note?
No. This page is a read-only viewer. There are no controls to add, edit, or delete entries from here.