Skip to content

docs: backfill CHANGELOG [4.9.4] to match release notes#3395

Merged
Yeraze merged 1 commit into
mainfrom
docs/changelog-4.9.4
Jun 10, 2026
Merged

docs: backfill CHANGELOG [4.9.4] to match release notes#3395
Yeraze merged 1 commit into
mainfrom
docs/changelog-4.9.4

Conversation

@Yeraze

@Yeraze Yeraze commented Jun 9, 2026

Copy link
Copy Markdown
Owner

Summary

The [4.9.4] CHANGELOG section was cut from [Unreleased] when the release branch was prepared, so it captured only a subset of what actually shipped in v4.9.4. Several PRs that are part of the release merged without their own CHANGELOG entries. This backfills them so CHANGELOG.md matches the v4.9.4 GitHub release notes.

Added to [4.9.4]

Features: {DATE}/{TIME} Auto Announce tokens (#3382), MeshCore packet-monitor JSONL export (#3391), system appearance theme (#3344).
Bug Fixes: Dashboard Map Pin Style (#3364), MeshCore "Connecting…" state (#3380).
Security (new subsection): Map Analysis positions endpoint viewOnMap/private-position gate (#3365/#3366).
Dependencies (new subsection): the 11 Dependabot bumps (#3367#3378).

Issues Resolved

None (documentation only).

Testing

  • Docs-only change; CHANGELOG content now matches the published release notes.

🤖 Generated with Claude Code

The [4.9.4] section captured only the entries present in [Unreleased] when
the release branch was cut. Add the remaining changes that shipped in
v4.9.4 but merged without their own CHANGELOG entries: {DATE}/{TIME}
tokens (#3382), MeshCore JSONL export (#3391), system theme (#3344),
Map Pin Style fix (#3364), MeshCore connecting state (#3380), the Map
Analysis security gate (#3365/#3366), and the 11 dependency bumps.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown

Claude finished @Yeraze's task —— View job


PR Review: CHANGELOG [4.9.4] Backfill

Review Tasks:

  • Read and analyze the CHANGELOG.md changes
  • Check formatting consistency and structure
  • Verify content appropriateness for a CHANGELOG
  • Provide comprehensive review feedback

Code Quality & Best Practices:

  • Assess CHANGELOG formatting standards
  • Review entry categorization and organization

Potential Issues:

  • Check for any formatting inconsistencies
  • Verify release note accuracy

Performance/Security/Test Coverage:

  • Assess (N/A for documentation changes)

Review Summary

This is a well-executed documentation improvement that backfills missing CHANGELOG entries for the v4.9.4 release. The changes are appropriate and follow excellent practices.

✅ Strengths

Formatting & Structure:

  • Excellent consistency with existing CHANGELOG format
  • Proper use of markdown headers (## for version, ### for categories)
  • Consistent bullet point formatting with -- prefix
  • Appropriate use of bold for feature/fix titles
  • Correct PR reference formatting ((#XXXX))

Content Quality:

  • Comprehensive coverage of missing features that shipped in v4.9.4
  • Well-organized categorization with new Security and Dependencies sections
  • Detailed, technical descriptions that explain both what changed and why it matters
  • Clear problem-solution narrative for bug fixes (explains the issue and the resolution)

New Section Additions:

✅ Technical Accuracy

The entries accurately reflect significant changes that should be documented:

✅ No Issues Found

  • No formatting inconsistencies detected
  • No security concerns (documentation-only change)
  • No performance implications
  • No test coverage needed (CHANGELOG update)
  • No code quality issues

Recommendation

✅ APPROVED - This PR successfully achieves its stated goal of making the CHANGELOG match the published v4.9.4 release notes. The additions are well-written, properly formatted, and provide valuable documentation for users reviewing what changed in the release.

This type of post-release documentation cleanup is exactly the right approach when CHANGELOG entries were missed during the release preparation process.


@Yeraze Yeraze merged commit b231f46 into main Jun 10, 2026
19 checks passed
@Yeraze Yeraze deleted the docs/changelog-4.9.4 branch June 10, 2026 01:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant