docs(CHANGELOG): restructure entries by release version

[kjdev]

Summary by CodeRabbit

• Documentation
  • Reworked the changelog into a standard versioned format for easier release tracking.
  • Added a new 0.2.1 release entry with dependency updates.
  • Reorganized the prior 0.2.0 notes into clearer sections for added and changed items.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated CHANGELOG.md to use Keep a Changelog/SemVer formatting, added a 0.2.1 release entry with dependency changes, and reorganized the prior release notes into structured Added and Changed sections.

Changes

Changelog format refresh

Layer / File(s)	Summary
Release notes restructure CHANGELOG.md	Added the changelog preamble, introduced the 0.2.1 dependency entry, and reformatted 0.2.0 into Added and Changed subsections.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A bunny hops through release notes bright,
With tidy headings set just right.
🐇 Dates and changes line up neat,
Old hash trails fade from view complete,
A carrot-bright changelog now takes flight.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: reorganizing CHANGELOG entries by release version.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/changelog

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[kjdev]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

🧹 Nitpick comments (2)

CHANGELOG.md (2)

6-23: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Add [Unreleased] section and comparison links.

Keep a Changelog format recommends:

1. An [Unreleased] section at the top to track upcoming changes.
2. Comparison links at the bottom of the file (e.g., [0.2.1]: https://github.com/user/repo/compare/v1.0.1...v1.0.2).

These are missing and should be added for full format compliance.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` around lines 6 - 23, The changelog is missing the standard Keep
a Changelog scaffolding: add an [Unreleased] section at the top of CHANGELOG.md
above the current 0.2.1 entry, and add comparison reference links at the bottom
for the existing version headings. Update the file structure so future changes
go under [Unreleased], and include the version link definitions matching the
existing release tags.

---

6-11: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Consider using standard Keep a Changelog categories.

The Dependencies subsection (Line 8) is not one of the standard Keep a Changelog categories (Added, Changed, Deprecated, Removed, Fixed, Security). Dependency bumps are typically placed under Changed. Using non-standard categories reduces compatibility with changelog parsers and tooling.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` around lines 6 - 11, The changelog entry uses a non-standard
Keep a Changelog subsection for a dependency bump; move this update under the
standard Changed category instead. Update the release note in CHANGELOG.md so
the nxe-json submodule bump is grouped with other changed items, keeping the
existing version entry and wording intact while replacing the Dependencies
heading with Changed.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@CHANGELOG.md`:
- Around line 6-23: The changelog is missing the standard Keep a Changelog
scaffolding: add an [Unreleased] section at the top of CHANGELOG.md above the
current 0.2.1 entry, and add comparison reference links at the bottom for the
existing version headings. Update the file structure so future changes go under
[Unreleased], and include the version link definitions matching the existing
release tags.
- Around line 6-11: The changelog entry uses a non-standard Keep a Changelog
subsection for a dependency bump; move this update under the standard Changed
category instead. Update the release note in CHANGELOG.md so the nxe-json
submodule bump is grouped with other changed items, keeping the existing version
entry and wording intact while replacing the Dependencies heading with Changed.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 010519e3-91c1-462d-82f7-df702320f87c

📥 Commits

Reviewing files that changed from the base of the PR and between 4ff7c49 and 2c51eef.

📒 Files selected for processing (1)

• CHANGELOG.md