fix(release): rebuild fatal UTF-8 SBOM evidence on live main - #199
Conversation
|
Warning Review limit reached
Next review available in: 25 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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 |
Fresh protected-main test-first successor for #112 on exact base
1f662dfcb80b08ba25d8ec9bff80bd433c49b6ed.Current exact head
5c15d42525e9b912f92a04585a7be6544a217f78is intentionally test-only RED. It preserves the valid release-evidence path, adds a malformed UTF-8 retained-SBOM regression, and separately pins valid-UTF-8 invalid-JSON failure so byte decoding and JSON syntax remain distinct fail-closed boundaries.Protected main still uses
readFileSync(sbomPath, "utf8"), which replacement-decodes malformed bytes beforeJSON.parse; the malformed-byte regression must fail until the production reader is narrowed. Historical #113 checks/reviews/scanner evidence do not transfer.After exact RED proof, apply only the narrow production remedy: read exact SBOM bytes, decode using fatal UTF-8, then parse JSON; continue hashing the retained original bytes. Keep Draft until GREEN plus fresh exact-head application CI, reviewer-ci, protected-base eligible central Security Scan, current reviews/threads, and live-base identity are revalidated.