Repository navigation
CHANGELOG cleanup: fold post-release-cut merges into 4.1.0, dedupe section headings - #157
Merged
Merged
Conversation
…e headings The parallel merges after the 4.1.0 release cut (#152-#156: loop CPU profiling, the multi-cylinder RPM fix, assignable LED status modes, and the download-throughput regression fix) each appended their entries under a fresh [Unreleased] heading, leaving that block with three separate 'Fixed' sections while FIRMWARE_VERSION on this branch is already 4.1.0 - everything here ships in the release PR #150 promotes. Fold those entries into the [4.1.0] section, one heading per category, and refresh the release intro: the date, the DOVEX byte-for-byte claim (stock logs now drop the three temperature columns), the cylinder_count RPM caveat, and the beta-only note (SensorEgg gained the scanner race-gating fix, and the profiler is a second beta-only flag). Entry text is moved verbatim except where the release-cut entries named the setting by its mid-cycle key: 'rev_limit' references now read 'target_rpm' (the key 4.1.0 actually ships), the temp1_alert_c entry is marked SensorEgg-only, and the rename entry notes the old key only ever existed on the beta channel. Also merges the same mass-merge duplication in released sections - 3.0.1 carried three 'Added', three 'Changed' and two 'Fixed' headings, 2.2.0 two 'Changed' - moving entries verbatim, and adds the missing blank line before 4.0.0's 'Fixed'. An empty [Unreleased] heading stays at the top. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MqSstYTWPhm3TZ3PxXs4hk
Coverage — host-testable units📂 Overall coverage
📄 File coverage
|
7 of 13 tasks
8 of 13 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docs-only restructure of
CHANGELOG.md— no entry is dropped; text moves verbatim except for the deliberate edits listed below. The mass-merge frenzy after the 4.1.0 release cut left the file discombobulated in two ways, and this fixes both:1. The post-#151 merges belong in the 4.1.0 section, not
[Unreleased]. #152–#156 (loop CPU profiling, the multi-cylinder RPM fix, assignable LED status modes, the download-throughput regression fix) each appended entries under[Unreleased]— which had accumulated three separate### Fixedheadings — butFIRMWARE_VERSIONon this branch is already4.1.0and everything here ships when #150 merges. Those entries are now folded into[4.1.0](one heading per category), the date is bumped to 2026-08-24, and the release intro is corrected to match the merged reality:nantemperature columns (13 vs 16 data columns; readers key off the CSV header).cylinder_countRPM fix (readings change for anyone who had it set above 1).2. Released sections carried the same duplication.
[3.0.1]had three### Added, three### Changed, and two### Fixedheadings;[2.2.0]had two### Changed. Duplicates are merged (entries moved verbatim, one heading per category), and the missing blank line before[4.0.0]'s### Fixedis added. An empty[Unreleased]heading stays at the top per Keep a Changelog.Deliberate text edits (the release cut's entries named the setting by its mid-cycle beta key, which 4.1.0 never ships):
rev_limitreferences in the NeoPixel and overrev entries now readtarget_rpm; thetemp1_alert_centry is marked SensorEgg-only and points at theegtstatus mode (both post-#154/#155 reality); and the rename entry notes the old key only ever existed on the beta channel.Merge this before #150 so the release promotes the cleaned changelog. Not renamed here (flagging instead): three plan records share the number 0012 (
0012-download-throughput-regression-deepdive,0012-led-status-modes,0012-tach-rpm-single-pickup), and open PR #148 also calls itself plan 0011 — same number as profiling. Renumbering would break the "plan NNNN" citations already in commit messages and these changelog entries, so that's left as a maintainer call.Type of change
How it was verified
rev_limit/temp1_alert_cedits are the only allowed exceptions), and each.replace()asserts its target text exists.Checklist
CHANGELOG.mdupdated — this PR is the changelog changeARCHITECTURE.md/CLAUDE.mdupdated — n/a, no module or interface changedtests/— n/a, no codeRelated issues
Companion to release PR #150 (its description is updated to match). Merge order: this → #150.
🤖 Generated with Claude Code
https://claude.ai/code/session_01MqSstYTWPhm3TZ3PxXs4hk
Generated by Claude Code