Conversation
The deploy-production job required deploy-staging, but staging only runs on push events. Manual workflow_dispatch with environment=production was always skipped because staging was skipped. Use always() with result checks so production runs when staging succeeds or is skipped. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eslint-plugin@8.56.1 requires parser@^8.56.1 as a peer dependency but package.json pinned parser@^6.2.0, causing npm ci ERESOLVE failures in CI. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
chittyregistry | 881e062 | Mar 17 2026, 03:00 AM |
|
Warning Rate limit exceeded
⌛ 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 ignored due to path filters (1)
📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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 |
|
@coderabbitai review |
|
Closing: conflicts with main. Will rebase if still needed. |
1 participant
Summary
@typescript-eslint/parserfrom^6.2.0to^8.56.1npm ciERESOLVE failures in CITest plan
npm cipasses🤖 Generated with Claude Code