14 / 51 · 24 Technical Writing for QA · Release Notes and Checklists← prev⊞ allnext →☰ Read as one page
2.6Change Logs and Version Histories
A change log tracks every release over time. It serves as a historical record for debugging ("when did this behavior change?"), customer support ("which version introduced this feature?"), and auditing.
Change Log Format (Keep a Changelog)
# Changelog
## [2.4.1] -- 2026-02-14
### Added
- Multi-currency checkout (EUR, GBP, JPY)
### Fixed
- Cart total rounding error on discounted orders (SHOP-1189)
### Changed
- Search reindexing performance improved (45min → 12min)
## [2.4.0] -- 2026-01-31
### Added
- Wishlist sharing via link
### Fixed
- Password reset email not sent for accounts with + in email address
### Removed
- Legacy v1 API endpoints (deprecated since v2.0)
Conventions (from keepachangelog.com):
- Added for new features
- Changed for changes to existing functionality
- Deprecated for features that will be removed
- Removed for features that were removed
- Fixed for bug fixes
- Security for vulnerability fixes