Remove release notes page and link to the github release instead#125
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 0 minutes and 56 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughRemoved the standalone v0.11.0 release notes page and its navigation entry, added a consolidated "Releases" page and a "Recent releases" homepage section, and changed the announcement banner to link externally to the GitHub v0.11.0 release. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
s-adamantine
force-pushed
the
claude/elegant-haslett
branch
from
0308472 to
7bc13f6
Compare
s-adamantine
changed the title
- Update announcement banner to link to GitHub release instead of local page - Add /reference/releases page listing all lexicon releases - Add Releases entry to sidebar navigation - Remove local release notes page (release-notes-v0-11-0.md)
s-adamantine
force-pushed
the
claude/elegant-haslett
branch
from
7bc13f6 to
9803a18
Compare
![coderabbitai[bot]](https://avatars.github.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
pages/index.md (1)
12-13: Optional: Consider date format style.Some style guides recommend adding a comma after the year in month-day-year dates (e.g., "April 9, 2026,"). However, the current format is widely accepted and clean. This is purely a stylistic choice.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@pages/index.md` around lines 12 - 13, Update the two release lines "[Lexicon v0.11.2] — April 9, 2026" and "[Lexicon v0.11.0] — April 7, 2026" to use the month-day-year comma style by appending a comma after the year (e.g., change to "April 9, 2026," and "April 7, 2026,") so the date format is consistent with the suggested style guide; leave link URLs and version labels unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@pages/index.md`:
- Around line 10-14: The "Recent releases" list under the "## Recent releases"
header in pages/index.md omits v0.11.1; update that list to include an entry for
"Lexicon v0.11.1 — April 8, 2026" (matching the format of the existing bullets
for v0.11.2 and v0.11.0), or alternatively add a brief clarifying sentence below
the list explaining why only selected releases are shown (e.g., "Only
major/minor highlights are shown; see /reference/releases.md for the full list")
so the homepage and /reference/releases.md remain consistent.
---
Nitpick comments:
In `@pages/index.md`:
- Around line 12-13: Update the two release lines "[Lexicon v0.11.2] — April 9,
2026" and "[Lexicon v0.11.0] — April 7, 2026" to use the month-day-year comma
style by appending a comma after the year (e.g., change to "April 9, 2026," and
"April 7, 2026,") so the date format is consistent with the suggested style
guide; leave link URLs and version labels unchanged.
🪄 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: 6e12c6be-e21b-4e02-83b4-85d39a1571c3
📒 Files selected for processing (5)
components/AnnouncementBanner.jslib/navigation.jspages/index.mdpages/reference/release-notes-v0-11-0.mdpages/reference/releases.md
💤 Files with no reviewable changes (1)
- pages/reference/release-notes-v0-11-0.md
✅ Files skipped from review due to trivial changes (2)
- components/AnnouncementBanner.js
- pages/reference/releases.md
🚧 Files skipped from review as they are similar to previous changes (1)
- lib/navigation.js
| ## Recent releases | ||
|
|
||
| - [Lexicon v0.11.2](https://github.com/hypercerts-org/hypercerts-lexicon/releases/tag/v0.11.2) — April 9, 2026 | ||
| - [Lexicon v0.11.0](https://github.com/hypercerts-org/hypercerts-lexicon/releases/tag/v0.11.0) — April 7, 2026 | ||
|
|
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify v0.11.1 exists in the releases page
rg -n 'v0\.11\.1' pages/reference/releases.mdRepository: hypercerts-org/documentation
Length of output: 188
Include v0.11.1 in the "Recent releases" section or document why it's excluded.
The "Recent releases" section lists v0.11.2 and v0.11.0, but v0.11.1 (April 8, 2026) exists in the full releases table at /reference/releases.md. For consistency across the documentation, either add v0.11.1 to the homepage highlights or clarify in the content why only certain releases are displayed.
🧰 Tools
🪛 LanguageTool
[style] ~12-~12: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...exicon/releases/tag/v0.11.2) — April 9, 2026 - [Lexicon v0.11.0](https://github.com/...
(MISSING_COMMA_AFTER_YEAR)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@pages/index.md` around lines 10 - 14, The "Recent releases" list under the
"## Recent releases" header in pages/index.md omits v0.11.1; update that list to
include an entry for "Lexicon v0.11.1 — April 8, 2026" (matching the format of
the existing bullets for v0.11.2 and v0.11.0), or alternatively add a brief
clarifying sentence below the list explaining why only selected releases are
shown (e.g., "Only major/minor highlights are shown; see /reference/releases.md
for the full list") so the homepage and /reference/releases.md remain
consistent.
1 participant
Summary
pages/reference/release-notes-v0-11-0.md) in favor of the canonical GitHub Releases location