fix(ci): correct release changelog generation #28

Merged

starkSV merged 1 commit from fix/changelog-generation into main

2026-07-13 11:18:24 +05:30

starkSV commented

2026-07-13 11:18:07 +05:30

(Migrated from github.com)

Summary

Adds .github/workflows/cli-release.yml to the changelog path filter (was excluding CI-only changes)
Filters out chore(release): bump commits, which land after their own tag and were leaking into the next release's changelog
Falls back to a generic line if a release genuinely has nothing else to show

Why

v0.3.4's changelog showed the v0.3.3 version-bump commit instead of the actual linux-arm64 change -- already corrected the published release notes manually, this fixes it going forward

Test plan

Verified the fixed git log command produces the correct single-line changelog for v0.3.3..v0.3.4

## Summary - Adds .github/workflows/cli-release.yml to the changelog path filter (was excluding CI-only changes) - Filters out chore(release): bump commits, which land after their own tag and were leaking into the next release's changelog - Falls back to a generic line if a release genuinely has nothing else to show ## Why - v0.3.4's changelog showed the v0.3.3 version-bump commit instead of the actual linux-arm64 change -- already corrected the published release notes manually, this fixes it going forward ## Test plan - Verified the fixed git log command produces the correct single-line changelog for v0.3.3..v0.3.4

coderabbitai[bot] commented

2026-07-13 11:18:15 +05:30

(Migrated from github.com)

Warning

Review limit reached

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

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 8e9733d1-edbc-41bc-a78c-e76a691c7b7c

📥 Commits

Reviewing files that changed from the base of the PR and between e1151ff0cf and 1d5fc9c0f5.

📒 Files selected for processing (1)

.github/workflows/cli-release.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch fix/changelog-generation

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

> [!WARNING] > ## Review limit reached > > `@starkSV`, you've reached your PR review limit, so we couldn't start this review. > > **Next review available in:** **32 minutes** > > Enable **[usage-based reviews](https://app.coderabbit.ai/settings/billing?tab=usage&orgId=47e9434f-e709-482d-ae08-cc95f1974bac)** in Billing to review now. Otherwise, wait until the next included review is available. > You're only billed for reviews past your plan's rate limits ($0.25/file). > > <details> > <summary>How can I continue?</summary> > > 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. > > </details> > > > <details> > <summary>How do review limits work?</summary> > > 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](https://docs.coderabbit.ai/management/plans#rate-limits) for additional details. > > </details> > > <details> > <summary>Review details</summary> > > <details> > <summary>⚙️ Run configuration</summary> > > **Configuration used**: defaults > > **Review profile**: CHILL > > **Plan**: Pro Plus > > **Run ID**: `8e9733d1-edbc-41bc-a78c-e76a691c7b7c` > > </details> > > <details> > <summary>📥 Commits</summary> > > Reviewing files that changed from the base of the PR and between e1151ff0cf26459ce9fd14fa55afa23d3d3a6a1c and 1d5fc9c0f559866487237046b1cedc09a5ff98b7. > > </details> > > <details> > <summary>📒 Files selected for processing (1)</summary> > > * `.github/workflows/cli-release.yml` > > </details> > > </details>   <details> <summary>✨ Finishing Touches</summary> <details> <summary>🧪 Generate unit tests (beta)</summary> - [ ]  Create PR with unit tests - [ ]  Commit unit tests in branch `fix/changelog-generation` </details> </details>   --- Thanks for using [CodeRabbit](https://coderabbit.ai?utm_source=oss&utm_medium=github&utm_campaign=starkSV/windows-iso-downloader&utm_content=28)! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. <details> <summary>❤️ Share</summary> - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code) </details> <sub>Comment `@coderabbitai help` to get the list of available commands.</sub>