Conversation
…abel match, changeset description - Add permissions: contents: read / pull-requests: read to changeset.yml - Use jq exact match for skip-changeset label (prevent partial name collision) - Pin pnpm to '9' in publish.yml (reproducible CI installs) - Replace vague changeset description with specific user-facing bullets Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ipeline-to-changesets Migrate release pipeline to changesets (PUBLISHING.md standard)
chore: promote dev → staging
|
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: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (8)
Note
|
Summary
What this ships
Changeset migration (publish.yml) + all accumulated features since last release.
When merged,
publish.ymlfires → creates "chore: version packages" PR → merge that to publishhelixir@0.2.0to npm.Merge strategy
Merge commit (not squash) per branch strategy.