fix(ci): tolerate CRLF in uv.lock version check#35
Conversation
|
Warning Review limit reached
More reviews will be available in 19 minutes and 15 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy 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 |
Problem
The
v1.6.2release workflow failed onbuild-windowsat Verify version consistency:The Linux job passed the identical check. Root cause:
scripts/version.mjsmatches the uv.lock virtual-root block with a literal\n:re: /(name = "voiceflow"\nversion = ")([^"]+)(")/The Windows CI runner checks out with
core.autocrlf=trueand there is no.gitattributespinninguv.lockto LF, so the file lands with CRLF and\nnever matches\r\n. This is the new version-drift guard added this cycle (didn't exist for the v1.6.1 release), so the regression only surfaced now.Fix
Make the separator CRLF-tolerant:
\n→\r?\n. Verified the regex matches both LF and CRLF inputs, and thebumpreplacement preserves the captured separator so it stays correct on either platform.