cd(cua-driver): bake latest version into install.sh after each release - #1517
Conversation
Adds a BAKED_VERSION sentinel block to libs/cua-driver/scripts/install.sh that the CD workflow updates automatically after every cua-driver-v* release. The install script now resolves the version in priority order: 1. CUA_DRIVER_VERSION env var (explicit pin — unchanged) 2. CUA_DRIVER_BAKED_VERSION (new — set at release time, no API call needed) 3. GitHub Releases API walk (fallback only — kept for safety) This eliminates the GitHub API call for the common case, fixing 403 errors that hermes users see on shared NAT/VPN IPs that hit the 60 req/hr unauthenticated rate limit. Also bumps per_page 40→100 on the API fallback so future releases never fall off the page. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
📝 WalkthroughWalkthroughThe PR implements automatic baking of CUA driver release versions into the installer script. The install script's version resolution now prioritizes environment pins, then checks a baked constant, then falls back to GitHub API queries (with increased pagination). A new CD workflow step automatically updates this constant when releasing from versioned tags. ChangesBaked version mechanism
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Summary
BAKED_VERSIONsentinel block tolibs/cua-driver/scripts/install.shthat the CD workflow updates automatically after everycua-driver-v*releasehermes computer-use installusers on shared NAT/VPN IPs that exhaust the 60 req/hr GitHub unauthenticated rate limitper_pagefrom 40 → 100 on the API fallback path so future releases never fall off the pageHow it works
install.shgains a sentinel block kept in sync by CI:The tag resolution block now tries the baked version before falling back to the API:
cd-swift-cua-driver.ymlgains a post-release step:Test plan
cua-driver-v*release and confirm the CD step commits an updatedCUA_DRIVER_BAKED_VERSIONline to maininstall.shand confirm it printslatest release: cua-driver-vX.Y.Zwithout making any GitHub API calls (check withtcpdumpor network proxy if needed)CUA_DRIVER_VERSION=0.1.8 ./install.shstill overrides the baked version correctly🤖 Generated with Claude Code