Problem
CHANGELOG.md is significantly out of date. The latest formal entry is [2.3.0-rust] - 2026-03-08, but the current version is 2.6.24 (released 2026-03-22). At least 21 patch/minor versions (2.3.1 through 2.6.24) are missing from the changelog entirely.
The [Unreleased] section contains only GUI Forwarding features, but many other features have been shipped in versions 2.4.x–2.6.x as evidenced by:
- README.md documents many features like
azlin health, azlin logs, --os flag, compound naming, etc.
- pyproject.toml shows version 2.6.24
- Git history shows version bumps through 2.6.24
Impact
- Users cannot tell what changed between releases
- The changelog provides false confidence that 2.3.0-rust is the latest stable release
- Developers cannot reference what was introduced in which version
Fix
Add changelog entries for all versions from 2.3.1 through 2.6.24, following the existing [Keep a Changelog]((keepachangelog.com/redacted) format.
At minimum, create stub entries for each version that was released, extracted from git commit history:
git log --oneline v2.3.0-rust..HEAD
Suggested Improvement
Consider automating changelog generation as part of the release process (e.g., using the existing changelog-generator GitHub Actions workflow in .github/).
Generated by Documentation Freshness Checker
Problem
CHANGELOG.mdis significantly out of date. The latest formal entry is[2.3.0-rust] - 2026-03-08, but the current version is 2.6.24 (released 2026-03-22). At least 21 patch/minor versions (2.3.1 through 2.6.24) are missing from the changelog entirely.The
[Unreleased]section contains only GUI Forwarding features, but many other features have been shipped in versions 2.4.x–2.6.x as evidenced by:azlin health,azlin logs,--osflag, compound naming, etc.Impact
Fix
Add changelog entries for all versions from 2.3.1 through 2.6.24, following the existing [Keep a Changelog]((keepachangelog.com/redacted) format.
At minimum, create stub entries for each version that was released, extracted from git commit history:
Suggested Improvement
Consider automating changelog generation as part of the release process (e.g., using the existing
changelog-generatorGitHub Actions workflow in.github/).