Skip to content

chore: update npm metadata for packages to be released#135

Merged
jithin23-kv merged 1 commit into
masterfrom
chore/update-package-metadata
Jun 29, 2026
Merged

chore: update npm metadata for packages to be released#135
jithin23-kv merged 1 commit into
masterfrom
chore/update-package-metadata

Conversation

@jithin23-kv

@jithin23-kv jithin23-kv commented Jun 29, 2026

Copy link
Copy Markdown
Collaborator

Problem

The package.json metadata was not present for the packages that were going to be released

Solution

Add metadata and engine field foo node in package.json of three packages

Checklist

  • npm run build passes
  • npm run typecheck passes
  • npm run build:catalog:check passes (if evaluators or suites changed)
  • Tested against a local target (if evaluator added or changed)
  • No secrets, .env, or .opfor/ artifacts committed
  • PR title follows <type>: <what changed> — e.g. feat: add SSRF evaluator

Evaluator checklist (skip if no evaluator added)

  • id is unique across all evaluators
  • pass_criteria and fail_criteria are specific, not vague
  • severity matches actual risk (critical = RCE / data breach)
  • standards mapping is correct
  • .test.yaml fixture included

@coderabbitai

coderabbitai Bot commented Jun 29, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 29 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b7e242b6-0266-49a3-b248-d9084c630936

📥 Commits

Reviewing files that changed from the base of the PR and between b8ff91f and 040a712.

📒 Files selected for processing (3)
  • runners/cli/package.json
  • runners/mcp/package.json
  • runners/sdk/package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/update-package-metadata

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.

@jithin23-kv jithin23-kv merged commit f56c71e into master Jun 29, 2026
7 checks passed
@jithin23-kv jithin23-kv deleted the chore/update-package-metadata branch June 29, 2026 13:49
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.

2 participants