Conversation
|
Warning Review limit reached
Next review available in: 6 minutes Limit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the 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 within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe update publishes Lychee v7.7.4 security release notes, reclassifies v7.7.3, and adds two external security researchers to the support page. ChangesRelease publication
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: 🟡 Moderate · up to The PR adds v7.7.4 release information, but the update endpoint could advertise that release before it is available, causing users to be directed to an unavailable version. Researcher avatar names are also not preserved as image text, and minor release-note typos remain; merge should wait for the release-timing issue to be resolved or explicitly accepted. Poem
🚥 Pre-merge checks | ✅ 1✅ Passed checks (1 passed)
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 |
ildyria
changed the title
ildyria
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 4185f0ab-0541-4c79-865d-218e0173b277
📒 Files selected for processing (3)
src/content/docs/docs/getting-started/releases.mdsrc/data/releases.tssrc/pages/support.astro
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.
| }, | ||
| { | ||
| title: 'd3do-23 (Wu Wenhao)', | ||
| image: { | ||
| src: 'https://avatars.githubusercontent.com/u/73107878?v=4', | ||
| alt: 'd3do-23', | ||
| }, | ||
| }, | ||
| { | ||
| title: 'skeletonsec', | ||
| image: { | ||
| src: 'https://avatars.githubusercontent.com/u/298925831?v=4', | ||
| alt: 'skeletonsec', | ||
| }, | ||
| } | ||
|
|
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Preserve the avatar metadata when rendering.
The new entries provide image.alt, but ItemGrid4 currently renders a raw <img> with hard-coded alt="A bird."; Features5 forwards these items to that renderer. (raw.githubusercontent.com) This discards the researcher names and bypasses src/components/common/Image.astro. Update src/components/ui/ItemGrid4.astro to use the shared component and pass alt={image.alt}.
Proposed renderer fix
+import Image from '~/components/common/Image.astro';
+
-<img src={image.src} alt="A bird." class=" rounded-full h-20 w-20" />
+<Image src={image.src} alt={image.alt} width={80} height={80} layout="fixed" class="rounded-full h-20 w-20" />Sources: Coding guidelines, MCP tools
1 participant
Summary by CodeRabbit
New Features
Bug Fixes
Documentation