Problem
docs/QUICK_REFERENCE.md references version 2.6.17 but the current release is 2.7.0.
The file was last updated on 2026-03-12 and has not been updated with the version bumps that occurred since then (2.6.17 → 2.6.37 → 2.7.0).
Impact
Users who check the Quick Reference to verify they have the latest version will see a stale version number and may think their installation is up to date when it is not, or be confused about which version the docs apply to.
Suggested Fix
- Update the version reference in
docs/QUICK_REFERENCE.md from 2.6.17 to the current release version
- Consider automating this as part of the release process (e.g., a sed substitution in the release workflow that updates version numbers in key docs files)
Context
- Current
pyproject.toml version: 2.7.0
- Most recent git commit: bumped
2.6.36 → 2.6.37
- QUICK_REFERENCE.md last updated: 2026-03-12
- Version shown in QUICK_REFERENCE.md:
2.6.17
Generated by Documentation Freshness Checker
Problem
docs/QUICK_REFERENCE.mdreferences version 2.6.17 but the current release is 2.7.0.The file was last updated on 2026-03-12 and has not been updated with the version bumps that occurred since then (2.6.17 → 2.6.37 → 2.7.0).
Impact
Users who check the Quick Reference to verify they have the latest version will see a stale version number and may think their installation is up to date when it is not, or be confused about which version the docs apply to.
Suggested Fix
docs/QUICK_REFERENCE.mdfrom2.6.17to the current release versionContext
pyproject.tomlversion:2.7.02.6.36 → 2.6.372.6.17