## Problem Dependency version bump changes are no longer being consistently included in the CHANGELOG. These entries are valuable for investigating production issues and incidents that may be related to library dependency changes. ## Context - Previously, versions like 4.25.0 and earlier included detailed `**deps:**` entries documenting dependency updates - Recent versions still have some dependency entries but the pattern appears inconsistent - This information is critical for incident investigation and root cause analysis ## Example of Missing Information When investigating the Apdex SLO violation (issue #1799), having a complete changelog of dependency updates would help identify if any library changes introduced the bug around early December. ## Action Items 1. Review changelog generation configuration (likely conventional-commits based) 2. Verify commit message format requirements for dependency updates 3. Ensure all `chore(deps):` or similar commits are properly captured in changelog generation 4. Consider if changelog generation tool or configuration has changed recently 5. Restore dependency entries to CHANGELOG for all recent versions ## Impact - Easier incident investigation and root cause analysis - Better tracking of when specific dependency versions were introduced - Improved visibility into potential breaking changes or regressions from library updates