Skip to content

Add 0.4 changelog entry for manifest navigation ordering#122

Merged
KayleeWilliams merged 1 commit into
mainfrom
KayleeWilliams/changelog-0-4-manifest-nav-order
Jul 2, 2026
Merged

Add 0.4 changelog entry for manifest navigation ordering#122
KayleeWilliams merged 1 commit into
mainfrom
KayleeWilliams/changelog-0-4-manifest-nav-order

Conversation

@KayleeWilliams

Copy link
Copy Markdown
Collaborator

Follow-up to #120, which merged without a docs/changelog/0-4.mdx entry.

Adds an "Agent-readability artifacts" section documenting the navigation-order sorting of manifest.pages (and sitemap.xml), the llms-full.txt legacy-groups-mode parity, and the deliberately unchanged BYOP generateAgentArtifacts input order.

No changeset: the package changeset (.changeset/manifest-pages-nav-order.md) already landed with #120; this PR is release-notes prose only.

🤖 Generated with Claude Code

Documents the agent-readability manifest page sorting from #120, the
llms-full.txt groups-mode parity, and the unchanged BYOP input order.
@pullfrog

pullfrog Bot commented Jul 2, 2026

Copy link
Copy Markdown

This run was cancelled 🛑

The workflow was cancelled before completion. Please check the link below for details.

Pullfrog  | View workflow run | via Pullfrog𝕏

@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

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: 23 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: dab97cc8-c170-4d4a-bede-a32387b066fb

📥 Commits

Reviewing files that changed from the base of the PR and between 07ccef9 and ae37147.

📒 Files selected for processing (1)
  • docs/changelog/0-4.mdx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch KayleeWilliams/changelog-0-4-manifest-nav-order

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

@KayleeWilliams KayleeWilliams merged commit 8a0737a into main Jul 2, 2026
4 checks passed
@KayleeWilliams KayleeWilliams deleted the KayleeWilliams/changelog-0-4-manifest-nav-order branch July 2, 2026 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant