ci: bump pipelock SHA pin to v2.4.0#11
Conversation
Pipelock v2.4.0 tagged 2026-05-09. Bump the SHA-pinned action ref so the verify-python CI smoke runs against the current shipped pipelock. SHA 9b38f69593b24964042dfeb1f13d7088832bf817 corresponds to git tag v2.4.0 in luckyPipewrench/pipelock. Verifier behaviour unchanged.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Pipelock v2.4.0 tagged 2026-05-09. Bump the SHA-pinned action ref so the verify-python CI Pipelock Scan step runs against the current shipped pipelock.
Changes
.github/workflows/ci.yml: pin updated frompipelock@7a3b7de... # v2.3.0topipelock@9b38f695... # v2.4.0. The new SHA corresponds to git tagv2.4.0inluckyPipewrench/pipelock.Not changed
The 0.2.0 EvidenceReceipt v2 work in flight on
feat/v0.2.0-evidence-receipt-v2is unaffected.