Skip to content

Chore/add metadata to packages#15

Merged
arxja merged 8 commits into
mainfrom
chore/add-metadata-to-packages
Jul 3, 2026
Merged

Chore/add metadata to packages#15
arxja merged 8 commits into
mainfrom
chore/add-metadata-to-packages

Conversation

@arxja

@arxja arxja commented Jul 3, 2026

Copy link
Copy Markdown
Owner

Summary by CodeRabbit

  • Documentation

    • Added starter README pages for the CLI, client, and server packages with install instructions and learning links.
    • Updated core package wording and package naming for consistency.
  • Chores

    • Added MIT license files across packages.
    • Updated package metadata for publishing, including version resets, descriptions, authorship, repository links, and public npm settings.
    • Added package-specific build/clean/dev settings and TypeScript configuration updates.

@coderabbitai

coderabbitai Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@arxja, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 39 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: e05e21dc-0ec5-4d38-9bbf-03d75153ba0e

📥 Commits

Reviewing files that changed from the base of the PR and between fedc0b7 and 8bf8f71.

📒 Files selected for processing (1)
  • packages/core/README.md
📝 Walkthrough

Walkthrough

This 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.

Changes

Package publishing readiness

Layer / File(s) Summary
CLI package license, docs, and metadata
packages/cli/LICENSE, packages/cli/README.md, packages/cli/package.json
Adds MIT LICENSE and README for @jet-queue/cli; updates package.json version, description, author, keywords, repository info, files, license, publishConfig, and sideEffects.
Client package license, docs, metadata, and tsconfig
packages/client/LICENSE, packages/client/README.md, packages/client/package.json, packages/client/tsconfig.json
Adds MIT LICENSE and README for jet-queue/client; updates package.json version, metadata, scripts (dev, clean), devDependencies, publishConfig, sideEffects; sets tsconfig rootDir and bun types.
Server package license, docs, and metadata
packages/server/LICENSE, packages/server/README.md, packages/server/package.json
Adds MIT LICENSE and README for @jet-queue/server; updates package.json version, description, license, author, repository info, files, keywords, clean script, publishConfig, and sideEffects.
Core README wording fix
packages/core/README.md
Updates package name casing and rewrites the introductory documentation link sentence.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested labels: documentation, dependencies

Suggested reviewers: arxja

Poem

A rabbit hops through packages three,
Adding licenses, docs, and metadata for free,
Cli, client, server, all dressed anew,
With publishConfig gleaming and sideEffects true,
Core's README gets a wordier hue! 🐰📦

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title matches the main change: adding package metadata across the workspace.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/add-metadata-to-packages

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.

❤️ Share

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between 30f279a and fedc0b7.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (11)
  • packages/cli/LICENSE
  • packages/cli/README.md
  • packages/cli/package.json
  • packages/client/LICENSE
  • packages/client/README.md
  • packages/client/package.json
  • packages/client/tsconfig.json
  • packages/core/README.md
  • packages/server/LICENSE
  • packages/server/README.md
  • packages/server/package.json

Comment thread packages/core/README.md Outdated
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
@arxja arxja merged commit cb43a88 into main Jul 3, 2026
2 checks passed
@arxja arxja deleted the chore/add-metadata-to-packages branch July 3, 2026 07:41
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