Skip to content

Wave-33 C11: brew/winget publish readiness SelfCheck - #273

Merged
KooshaPari merged 1 commit into
mainfrom
feat/sl-w33-c11-brew-readiness
Jul 14, 2026
Merged

Wave-33 C11: brew/winget publish readiness SelfCheck#273
KooshaPari merged 1 commit into
mainfrom
feat/sl-w33-c11-brew-readiness

Conversation

@KooshaPari

Copy link
Copy Markdown
Owner

Summary

  • Expand docs/ops/brew-winget-publish.md with a publish-readiness checklist (done template/checksum gates vs unpaid live tap / winget-pkgs).
  • Add scripts/brew-winget-publish-check.ps1 -SelfCheck asserting formula/manifest + fill-script anchors without claiming live brew/winget.
  • Cross-link channels/distribution/packaging README; live tap and microsoft/winget-pkgs remain unpaid.

Test plan

  • pwsh ./scripts/brew-winget-publish-check.ps1 -SelfCheck passes locally

Made with Cursor

Add publish-readiness checklist gates (checksum fill + formula/manifest
anchors) and hermetic SelfCheck; keep live tap/winget-pkgs explicitly unpaid.

Co-authored-by: Cursor <cursoragent@cursor.com>
@gemini-code-assist

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 16 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: ASSERTIVE

Plan: Pro

Run ID: c7257ac0-c828-487d-bf2f-52916712cb3f

📥 Commits

Reviewing files that changed from the base of the PR and between 3efb0d0 and 3fbbf46.

📒 Files selected for processing (5)
  • docs/ops/brew-winget-publish.md
  • docs/ops/distribution.md
  • packaging/README.md
  • packaging/channels.md
  • scripts/brew-winget-publish-check.ps1
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/sl-w33-c11-brew-readiness
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch feat/sl-w33-c11-brew-readiness

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.

@KooshaPari
KooshaPari merged commit e2130e4 into main Jul 14, 2026
54 of 55 checks passed
KooshaPari added a commit that referenced this pull request Jul 14, 2026
Conservative +2 from PII redaction helper (C02 L24) and Python OKF
adapter stub (C08 L75). Held L60/L109 already max; soft OTLP/jemalloc.

Co-authored-by: Cursor <cursoragent@cursor.com>
@KooshaPari
KooshaPari deleted the feat/sl-w33-c11-brew-readiness branch August 12, 2026 08:59
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