Revert #477: restore minimum_version 0.0.15, drop redistributable attr (unblock pinned-minimal consumers) - #536
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 31 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Reverts #477. Restores
minimum_version = "0.0.15"and removes theredistributable = falseattr from android-sdk, claude-code, edgedelta.Why
#477's
minimum_versionbump to 0.0.18 (required so old clients get a legible error instead of a raw decode failure on the newredistributableattr) hard-gates every consumer whose installed minimal ships stdlib < 0.0.18 — including conservative/pinned-minimal CI that pulls latest pkgs only for security fixes and never touches the three proprietary packages. Because the graph is loaded whole-catalog on every build and attr validation is closed, the new attr breaks those consumers regardless of their closure.Reverting unblocks them immediately. 0.0.18 is the fix going forward, but it can't retroactively help clients already on an older pin.
The build-servers exclusion of these three packages (inbox#290 / #284) is driven by this attr. With the attr removed,
is_redistributabledefaults to true and the upload/seal filters stop excluding them, so the next canonical build re-uploads the proprietary artifacts to the public cache, undoing the 2026-07-28 purge.Sequencing: this must be paired with a build-servers change that keeps the three packages out of the public cache independent of the pkgs attr (a name-based denylist), landed/deployed before or immediately after this merges — otherwise there is a re-exposure window on the next pkgs build. Do not merge this in isolation and leave it.
Kept open (not auto-merged) so the compliance follow-up can be sequenced deliberately.