Public changelog exists

No changelog means users have no reliable way to know what changed between versions, whether a bug they hit is fixed, or whether upgrading is safe. A changelog that stops at v1.2.0 when the project is now on v2.1.0 is a signal that the project is poorly maintained — the same signal that drives dependency abandonment decisions. iso-25010:2011 analysability covers this: a project where change history is opaque requires source-level investigation to understand its evolution. Following Keep a Changelog format provides a predictable structure that users can parse quickly for the entries that matter to them.

Create CHANGELOG.md at the project root following Keep a Changelog format. The latest entry must match the version in package.json:

# Changelog

## [2.1.0] - 2026-03-15

### Added
- New `query()` method replacing `fetchData()`
- TypeScript type exports for all public types

### Fixed
- Connection timeout now throws instead of hanging indefinitely

## [2.0.0] - 2026-02-01

### Changed
- BREAKING: Renamed `fetchData()` to `query()`
- Minimum Node.js version bumped to 18

### Removed
- CommonJS import support dropped

A changelog without dates, version numbers, or change categorization fails this check. An outdated changelog (not updated for the current version) also fails.