🔖 v2.0.0

[NatoBoram]

Summary by CodeRabbit

• Documentation
  • Updated changelog with comprehensive version 2.0.0 release notes, documenting new features, enhancements, and bug fixes.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new 2.0.0 release section to CHANGELOG.md with Added, Changed, Fixed, and Security subsections. Documents new features including run command, --from-current flag, directory copy settings, OpenCode AI adapter, PR template, and path canonicalization. Updates Unreleased references and reorganizes prior entries.

Changes

Cohort / File(s)	Summary
Release Notes CHANGELOG.md	Added v2.0.0 release section with new features (run command, --from-current flag, directory copy settings, OpenCode AI adapter, PR template, path canonicalization) and reorganized prior Unreleased entries into Added, Changed, Fixed, and Security subsections

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

This is a straightforward documentation update with no code logic to review—only changelog restructuring and release note documentation.

Poem

🐰 Version two hops into the light,
With shiny new features, oh what a sight!
The changelog grows with every new quest,
From run commands bright to canonicalization blessed! 🎉

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title '🔖 v2.0.0' is directly related to the pull request's main objective of releasing version 2.0.0, which is evidenced by the changelog updates creating a new 2.0.0 release section.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release/v2.0.0

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between a552612 and 21f2bde.

📒 Files selected for processing (1)

• CHANGELOG.md (2 hunks)

🧰 Additional context used

🪛 LanguageTool

CHANGELOG.md

[uncategorized] ~29-~29: The official name of this software platform is spelled with a capital “H”.
Context: ...ode AI adapter - Pull request template (.github/PULL_REQUEST_TEMPLATE.md) - Path canon...

(GITHUB)

🔇 Additional comments (2)

CHANGELOG.md (2)

19-19: Well-structured changelog following Keep a Changelog format.

The v2.0.0 release section is comprehensive and well-organized with clear subsections for Added, Changed, and Fixed entries. The BREAKING change is properly flagged, and each item includes sufficient context (examples, justifications, related settings). The format, date structure (YYYY-MM-DD), and version hierarchy all align with best practices.

Also applies to: 21-51

---

76-77: Verify version comparison links resolve correctly.

The GitHub comparison URLs follow the correct format for version tagging. Ensure the Git tags (v2.0.0, v1.0.0) exist in the repository so these links resolve properly when the release is published.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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.}