Skip to content

docs: consolidate duplicate CHANGELOG sections before the 0.2.0 cut - #60

Merged
jamesarich merged 1 commit into
mainfrom
docs/pre-0.2.0-changelog-audit
Aug 17, 2026
Merged

docs: consolidate duplicate CHANGELOG sections before the 0.2.0 cut#60
jamesarich merged 1 commit into
mainfrom
docs/pre-0.2.0-changelog-audit

Conversation

@jamesarich

Copy link
Copy Markdown
Collaborator

#57, #58 and #59 each added their own `[Unreleased]` entries and got rebased onto each other individually to resolve real code conflicts (see #59's merged history) — the CHANGELOG merges themselves left two artifacts behind:

  • Two separate `### Fixed` headers under `[Unreleased]`, with the Dictionary_ID fix listed under both. Consolidated into one, reordered to match this file's own established Added/Changed/Fixed/Notes order (see `[0.1.2]`).
  • A Notes bullet claiming "kzstd enforces no `Dictionary_ID`" as the reason wrong-dictionary decoding was silently wrong — true before this release's own Dictionary_ID validation, false by the time a reader reaches it a few bullets later. Rewritten to describe what the new check actually catches vs. what it still can't (raw-content dictionaries, or a frame declaring no ID).

Pure docs, no code change. Checked README and AGENTS.md for the same class of leftover — both are clean (no stale "enforces no Dictionary_ID" claims elsewhere, no duplicate sections). README's install snippet still correctly pins `0.1.2` (still the latest actual release) — that bump belongs with the real `chore(release): prepare v0.2.0` commit, not here, matching how #45/#53 split that work previously.

Three separate branches (#57 checksum, #58 dictionary-ID, #59 entropy/
multi-block) each added their own [Unreleased] entries and were rebased
onto each other individually; the CHANGELOG merges left two duplicate
artifacts:

- Two separate "### Fixed" headers under [Unreleased], with the
  Dictionary_ID fix listed under both (once briefly, once in full) --
  consolidated into one "### Fixed" section, keeping the more detailed
  wording, and reordered Added/Changed/Fixed/Notes to match this file's
  own established category order (see the [0.1.2] section).
- A "Notes" bullet claiming "kzstd enforces no Dictionary_ID" as the
  reason wrong-dictionary decoding was silently wrong -- true before this
  release's own Dictionary_ID validation landed a few bullets above it,
  false by the time a reader reaches it. Rewritten to describe what the
  new check actually catches (proper-format dictionaries with a
  mismatched embedded ID) and what it still can't (raw-content
  dictionaries, or a frame with no declared ID).

Signed-off-by: James Rich <james.a.rich@gmail.com>
@coderabbitai

coderabbitai Bot commented Aug 17, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jamesarich, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 27ffd6a9-6251-4a3f-9208-e72e29d77c79

📥 Commits

Reviewing files that changed from the base of the PR and between f30376b and f1a1394.

📒 Files selected for processing (1)
  • CHANGELOG.md

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@jamesarich
jamesarich enabled auto-merge August 17, 2026 21:55
@jamesarich
jamesarich added this pull request to the merge queue Aug 17, 2026
Merged via the queue into main with commit 1dcc507 Aug 17, 2026
8 checks passed
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