fix: pin Yarn canary to available ARM64 release - #175
Conversation
|
Understand this PR’s impact Explore downstream dependencies and potential security impact with Blast Radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe setup script now supports a benchmark version override and stricter canary version fetching. The benchmark workflow pins the benchmark version and skips result and version artifact uploads after cancellation. ChangesBenchmark version and artifact handling
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
The Yarn canary channel advertises
6.0.0-rc.21, but its Linux ARM64 npm binary returns HTTP 404. This aborts therunbenchmark during Hyperfine preparation and prevents result processing.Pin the benchmark job to the available
6.0.0-rc.20release and make setup's version reporting honorBENCH_ZPM_VERSION. Upload benchmark results and version information after failures so redirected diagnostic logs remain available.Validation:
Failing job: https://github.com/vltpkg/benchmarks/actions/runs/35588817974/job/106423763722
Summary by CodeRabbit