# Release notes template (single release)

Use this file for one release at a time: fill in the placeholders, delete the guidance in brackets, and publish.
For the running record of every version (a CHANGELOG.md), use the changelog template instead:
https://www.releasepad.io/blog/changelog-template/

Source and more formats: https://www.releasepad.io/resources/release-notes-templates/

<!-- ───────────────────────── TEMPLATE ───────────────────────── -->

## v[MAJOR.MINOR.PATCH] — [Month D, YYYY]

[One or two sentences summarizing the release. Lead with the biggest benefit. Skip this line for small patches.]

### New
- [Feature name]: [what the user can now do, in one sentence].
- [Feature name]: [what the user can now do, in one sentence].

### Improved
- [What got better and by how much, e.g. "Dashboards now load about twice as fast on large accounts."]

### Fixed
- [The symptom the user saw, then the fix, e.g. "Resolved a bug that signed some users out early."]

[Optional: Action required — anything a user or admin must do, with a deadline if there is one.]
[Optional: Learn more — one link to docs or a help article, only when the change earns it.]

<!-- ───────────────────────── FILLED-IN EXAMPLE ───────────────────────── -->

## v1.4.0 — March 12, 2026

Reports are easier to get out of the product this week, and dashboards are faster for everyone.

### New
- Bulk export: download any report as a CSV in one click.

### Improved
- Dashboards now load roughly twice as fast on large accounts.

### Fixed
- Resolved a bug that signed some users out early.

<!-- ───────────────────────── WRITING CHECKLIST ───────────────────────── -->

- Name each change in the user's words, not the ticket's ("Bulk export", not "feat: add CSV endpoint").
- One or two sentences per entry. Send detail to docs with a link.
- Group by category so readers can scan; keep the category names stable from release to release.
- Flag breaking changes and anything that needs action so they cannot be missed.
- Leave out internal work (dependency bumps, refactors) that users will never notice.
- Use one date format everywhere. YYYY-MM-DD is never ambiguous across regions.
