Repository navigation
Conversation
Add table rows for platform, shard-engine, platform-cloudflare, platform-node, and auth-ui, relocate the observability row next to its platform-family siblings, rewrite the "exactly two packages" prose to match the five packages on disk, and correct the advisor row's stale rule count (81 -> ~95, with a pointer to the live STATIC_LINTS array).
AGENTS.md is the file every coding agent reads to decide which package owns a change, and it has silently drifted out of sync with packages/* five times already (auth-ui, platform, platform-cloudflare, platform-node, shard-engine). Add check-agents-md-packages.js to the postinstall chain so a new package with no AGENTS.md mention fails the next install instead of going unnoticed.
check-sibling-peer-ranges.js only ever walked peerDependencies, so an exact @lunora/* dependencies pin drifting behind its sibling's current version was invisible. multi-semantic-release's "satisfy" bump mode only re-pins a consumer's dependencies on the consumer's own next release, so a rarely-releasing (or private, never-released) consumer can carry a stale pin indefinitely -- which means two published @lunora/* packages installed together can resolve two physical copies of a shared sibling. Add a second, report-only pass over dependencies (never failing the install, since mid-release-train drift is expected) alongside the existing exact-peer-pin gate. Baseline: 63 stale pins across 30 packages, captured below. Before (pre-sweep tree, this script): 63 warnings, one per stale pin, e.g. "packages/do depends on \"@lunora/platform-cloudflare\": \"1.0.0-alpha.1\" -- current is \"1.0.0-alpha.2\".", ending in a one-line summary count. After (post-sweep, next commit): 0 warnings.
63 exact dependencies pins across 30 packages had drifted behind the sibling's current published version -- @lunora/errors alone was split three ways (alpha.8/alpha.10/alpha.11 against a current alpha.11). Set every stale specifier to its dependency's current version field; version fields themselves are untouched (releases stay automation- owned). Regenerated pnpm-lock.yaml to match. Re-derivation after this commit reports 0 stale pins; the extended check-sibling-peer-ranges.js guard reports 0 dependency warnings.
|
Warning Review limit reached
Next review available in: 58 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (32)
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 |
❌ Deploy Preview for lunorash failed.
|
|
Thank you for following the naming conventions! 🙏 |
|
Thank you for confirming the Contributor License Agreement! 🙏 |
|
Closing: this PR was opened in error by an automated run, outside the scope of its task. No work is lost — the branch is retained on origin and this PR can be reopened at any time. Context: this branch predates the merges of #288 and #289, so much of its content is already on |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Branched before #288/#289 landed, so it needs a rebase onto current alpha before merge.
Commits
Files this branch still changes relative to alpha