release: 0.2.0

[pilat]

Bump version to 0.2.0 with updated CHANGELOG.

Summary by CodeRabbit

• Chores
  • Released version 0.2.0
  • Minimum Node.js version requirement updated to 22

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Version 0.2.0 release update: package.json version number incremented from 0.1.1 to 0.2.0, and CHANGELOG.md entry added documenting the minimum Node.js version requirement increase to version 22.

Changes

Cohort / File(s)	Summary
Version & Release Documentation package.json, CHANGELOG.md	Version bumped to 0.2.0; changelog entry added noting minimum Node.js version requirement increased to 22 (reflecting Node 20 EOL in April 2026)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A version hops forward with grace,
From one-point-one to twenty-point-oh!
Node twenty's time has passed its race,
Twenty-two now steals the show. ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'release: 0.2.0' clearly and concisely describes the main change in the pull request: bumping the version to 0.2.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 46ba2f8 and 441d6c7.

📒 Files selected for processing (2)

• CHANGELOG.md
• package.json

🔇 Additional comments (2)

CHANGELOG.md (1)

8-13: CHANGELOG entry structure looks good.

The entry follows the Keep a Changelog format correctly, and the additional context about Node 20's EOL date (April 2026) is helpful. However, please ensure the content accurately reflects the actual changes in this release (as noted in the package.json review).

package.json (1)

3-3: Verify the CHANGELOG entry about Node.js version requirement change.

The CHANGELOG states that the minimum Node.js version was "bumped to 22" in version 0.2.0. However, the git repository contains only this release commit, making it impossible to verify whether the engines.node field was actually changed from a previous value or was already set to ">=22.0.0".

Please clarify: Was the engines.node requirement actually changed in this release, or was it already >=22.0.0 in version 0.1.1? If it wasn't changed, the CHANGELOG entry should be revised to accurately reflect what's new in 0.2.0.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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 and usage tips.}