Conversation
Add comprehensive CHANGELOG.md documenting all releases from v1.0.2 through v1.2.0, plus a v1.2.1 entry for the changelog addition itself. Append changelog maintenance instructions to CLAUDE.md. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
📝 WalkthroughWalkthroughThe PR adds project documentation: a new CHANGELOG.md file documenting all historical releases from v1.0.2 through v1.2.1, and updates CLAUDE.md with changelog maintenance instructions for contributors. No functional code changes. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@CHANGELOG.md`:
- Around line 23-25: Update the forward reference in the CHANGELOG entry for
v1.1.12: replace "Same issue as v1.1.13" with wording that points backwards
(e.g., remove the forward reference or change it so v1.1.13's entry references
v1.1.12). Specifically edit the v1.1.12 paragraph that mentions `run-hook.cmd`
and the version strings "v1.1.12" / "v1.1.13" so the cross-reference correctly
indicates that v1.1.13 repeated the issue originally introduced in v1.1.12.
In `@CLAUDE.md`:
- Around line 58-60: Add a top-level "## Unreleased" heading to CHANGELOG.md as
a placeholder so contributors have an example section to add entries; insert the
"## Unreleased" header at the very top (above existing entries) and include one
example bullet showing the expected format (brief description + PR reference) or
a short note telling contributors to add entries there, following the existing
changelog style.
| ## v1.1.12 (2026-02-11) | ||
|
|
||
| - **Fix**: Added execute permissions to `run-hook.cmd`. Same issue as v1.1.13 - the polyglot script needs the executable bit set on Unix/POSIX systems (Linux, macOS). Windows is unaffected as it doesn't use Unix permission bits. |
There was a problem hiding this comment.
Forward reference in v1.1.12 entry reads backwards.
Line 25 says "Same issue as v1.1.13", but v1.1.12 predates v1.1.13 — the issue occurred first in v1.1.12 and recurred in v1.1.13. The cross-reference direction should be reversed: v1.1.13's entry should say "Same issue as v1.1.12", not the other way around.
📝 Suggested rewording
## v1.1.13 (2026-02-11)
-- **Fix**: Restored execute permissions on `run-hook.cmd` that were lost during a prior commit. Without execute permissions, the hook silently failed on Linux and macOS (Unix/POSIX systems) where file permission bits are enforced.
+- **Fix**: Restored execute permissions on `run-hook.cmd` that were lost during a prior commit (same issue as v1.1.12). Without execute permissions, the hook silently failed on Linux and macOS (Unix/POSIX systems) where file permission bits are enforced.
## v1.1.12 (2026-02-11)
-- **Fix**: Added execute permissions to `run-hook.cmd`. Same issue as v1.1.13 - the polyglot script needs the executable bit set on Unix/POSIX systems (Linux, macOS). Windows is unaffected as it doesn't use Unix permission bits.
+- **Fix**: Added execute permissions to `run-hook.cmd`. The polyglot script needs the executable bit set on Unix/POSIX systems (Linux, macOS). Windows is unaffected as it doesn't use Unix permission bits.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@CHANGELOG.md` around lines 23 - 25, Update the forward reference in the
CHANGELOG entry for v1.1.12: replace "Same issue as v1.1.13" with wording that
points backwards (e.g., remove the forward reference or change it so v1.1.13's
entry references v1.1.12). Specifically edit the v1.1.12 paragraph that mentions
`run-hook.cmd` and the version strings "v1.1.12" / "v1.1.13" so the
cross-reference correctly indicates that v1.1.13 repeated the issue originally
introduced in v1.1.12.
| ## Changelog | ||
|
|
||
| When making user-facing changes, update `CHANGELOG.md` in the project root. Add entries under an `## Unreleased` section at the top, following the existing format: brief description of what changed and why it matters to users, with PR references where applicable. |
There was a problem hiding this comment.
## Unreleased section is missing from CHANGELOG.md.
The guidance here tells contributors to add entries under ## Unreleased, but CHANGELOG.md itself has no such section and no example of it. A contributor following this instruction would need to know to create the section from scratch. Consider adding an empty ## Unreleased placeholder at the top of CHANGELOG.md so the format is self-evident.
📝 Suggested addition to CHANGELOG.md
# Changelog
All notable changes to this project are documented in this file.
+## Unreleased
+
## v1.2.1 (2026-02-19)🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@CLAUDE.md` around lines 58 - 60, Add a top-level "## Unreleased" heading to
CHANGELOG.md as a placeholder so contributors have an example section to add
entries; insert the "## Unreleased" header at the very top (above existing
entries) and include one example bullet showing the expected format (brief
description + PR reference) or a short note telling contributors to add entries
there, following the existing changelog style.
1 participant
Summary
CHANGELOG.mddocumenting all releases from v1.0.2 (initial release) through v1.2.0 (OpenCode support).CLAUDE.mdwith changelog maintenance instructions so future changes follow a consistent process.Test plan
CHANGELOG.mdrenders correctly on GitHubCLAUDE.mdchangelog section is appended correctly🤖 Generated with Claude Code
Summary by CodeRabbit