Skip to content

chore: revise CHANGELOG for dashboard action and links#382

Merged
pratyush618 merged 2 commits into
masterfrom
pratyush618-patch-1
Jul 7, 2026
Merged

chore: revise CHANGELOG for dashboard action and links#382
pratyush618 merged 2 commits into
masterfrom
pratyush618-patch-1

Conversation

@pratyush618

@pratyush618 pratyush618 commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator

Updated CHANGELOG.md to reflect changes in the dashboard build action and internal link updates.

Summary by CodeRabbit

  • Documentation
    • Updated the “Older releases” collapsible section to include releases 0.1.0–0.12.0.
    • Removed the previous 0.1.0–0.10.0 range and repositioned the section for clearer release navigation.

Updated CHANGELOG.md to reflect changes in the dashboard build action and internal link updates.
@github-actions github-actions Bot added the docs label Jul 7, 2026
@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 6 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

Run ID: f019544c-5d1b-4e0a-829e-8d5a9be3c3b1

📥 Commits

Reviewing files that changed from the base of the PR and between 292ae06 and b04eb9a.

📒 Files selected for processing (1)
  • docs/content/docs/resources/changelog.mdx
📝 Walkthrough

Walkthrough

The CHANGELOG.md collapsible "Older releases" section label range was updated from 0.1.0–0.10.0 to 0.1.0–0.12.0. The old collapsible wrapper was removed and replaced with a new one at a different location in the file.

Changes

Changelog collapsible section update

Layer / File(s) Summary
Update older releases range label
CHANGELOG.md
Replaced the collapsible entry labeled "Older releases (0.1.0 – 0.10.0)" with a new one labeled "Older releases (0.1.0 – 0.12.0)".

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested labels: documentation

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
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.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title is concise and points to the CHANGELOG update, which is the core of the change.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch pratyush618-patch-1

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

@pratyush618 pratyush618 changed the title Revise CHANGELOG for dashboard action and links chore: revise CHANGELOG for dashboard action and links Jul 7, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

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

Inline comments:
In `@CHANGELOG.md`:
- Around line 469-471: The changelog range label update is only applied in the
main changelog, leaving the docs copy out of sync. Update the matching “Older
releases” label in the downstream changelog entry in
docs/content/docs/resources/changelog.mdx so it matches the new range, and keep
both surfaces aligned when editing the shared changelog wording.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fbd775d1-e04e-4e96-bbe4-34446ad70754

📥 Commits

Reviewing files that changed from the base of the PR and between 1c80eed and 292ae06.

📒 Files selected for processing (1)
  • CHANGELOG.md

Comment thread CHANGELOG.md
Updated changelog to reflect internal link changes and added details for older releases.
@pratyush618 pratyush618 merged commit 321984b into master Jul 7, 2026
14 checks passed
@pratyush618 pratyush618 deleted the pratyush618-patch-1 branch July 7, 2026 05:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant