fix(cli): add repository field so provenance publish succeeds#48
Conversation
Publishing with provenance validates that package.json repository.url matches the source repo. apps/cli had no repository field, so the trusted-publishing release failed with E422 on cli (after config/core/search-ui had published). Add the repository field matching the other packages.
|
Warning Review limit reached
More reviews will be available in 22 minutes and 42 seconds. Learn how PR review limits work. To continue reviewing without waiting, enable usage-based billing in the billing tab. ⌛ How to resolve this issue?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 credits. 🚦 How do rate 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 see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Comment |
fix(cli): add repository field so provenance publish succeeds
The v2.0.6 release workflow published
config,core, andsearch-uiwith provenance, then failed oncli:apps/cli/package.jsonhad norepositoryfield, which provenance verification requires. (webhook-handleralready has one — it just never got its turn after cli failed.)This adds the
repositoryfield matching the other packages. After merge, re-cutting the v2.0.6 release will skip the three already-published packages and publishcli@2.0.6+webhook@2.0.6with valid provenance.