ci(deploy): bump runner Node to 22 for wrangler 4 - #3
Conversation
The first Doppler-driven deploy succeeded at fetching secrets but crashed at `wrangler deploy`: Wrangler requires at least Node.js v22.0.0. You are using v20.20.2. ubuntu-latest still ships Node 20 by default; pinning Node 22 via actions/setup-node fixes the deploy step. bunx invokes wrangler's CLI which then resolves `node` from PATH, so this is enough.
|
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. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
1 participant
Follow-up to #2. First Doppler-driven deploy succeeded at fetching secrets but
wrangler deploycrashed because the runner ships with Node 20. Pin Node 22 viaactions/setup-nodebefore the deploy step.