Chore/add metadata to packages#15
Conversation
…ate the client readme file
|
Warning Review limit reached
Next review available in: 39 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. 📝 WalkthroughWalkthroughThis PR adds MIT LICENSE files and README documentation to the cli, client, and server packages, updates their package.json files with richer metadata (description, author, keywords, repository, publishConfig, sideEffects), updates client tsconfig.json, and fixes wording in the core README. ChangesPackage publishing readiness
Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested labels: documentation, dependencies Suggested reviewers: arxja PoemA rabbit hops through packages three, 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
There was a problem hiding this comment.
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 `@packages/core/README.md`:
- Line 11: The README link text is too vague and should be made descriptive to
satisfy markdown linting. Update the existing JetQueue reference in the README
content to use meaningful anchor text such as “JetQueue docs” while keeping the
same URL, and ensure the change is made in the README entry that currently uses
the `[here]` link.
🪄 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: 09fcc964-6228-4073-aae8-c317b121c0bc
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (11)
packages/cli/LICENSEpackages/cli/README.mdpackages/cli/package.jsonpackages/client/LICENSEpackages/client/README.mdpackages/client/package.jsonpackages/client/tsconfig.jsonpackages/core/README.mdpackages/server/LICENSEpackages/server/README.mdpackages/server/package.json
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Summary by CodeRabbit
Documentation
Chores