move to latest vercel version

[piyush-jaiswal]

Summary by CodeRabbit

• Chores
  • Updated deployment workflows to install the latest Vercel CLI for both preview and production deployments.
  • Ensures up-to-date tooling, improved consistency across environments, and reduced maintenance of pinned versions.
  • No user-facing changes.

[coderabbitai]

Warning

Rate limit exceeded

@piyush-jaiswal has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 11 minutes and 3 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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.

📥 Commits

Reviewing files that changed from the base of the PR and between db50d29 and e4ffb02.

📒 Files selected for processing (2)

• .github/workflows/deploy_preview.yml (1 hunks)
• .github/workflows/deploy_production.yml (1 hunks)

Walkthrough

Updated two GitHub Actions workflows to install the Vercel CLI using vercel@latest instead of a pinned version. No other steps or logic changed.

Changes

Cohort / File(s)	Summary
GitHub Workflows .github/workflows/deploy_*.yml	Changed Vercel CLI install command from a pinned version to npm install --global vercel@latest; no other modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Block vercel deployment on test success #6 — Introduced workflows installing a pinned vercel@44.6.6; this PR switches those installs to vercel@latest, affecting the same step.

Poem

A bunny taps CI with gentle haste,
Swaps fixed for fresh—now Vercel’s “latest.”
Two YAML scrolls, a version’s flight,
Deploys hop on through day and night.
Ears up, tail bright—shipping just right! 🐇🚀

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ci/move-to-vercel-latest

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

.github/workflows/deploy_preview.yml (1)

31-31: Using vercel@latest in preview is fine; add traceability by logging the installed version.

Preview jobs are a good place to surface breaking changes early. To aid debugging when “latest” changes upstream, print the resolved CLI version after install.

Apply:

-              run: npm install --global vercel@latest
+              run: |
+                npm install --global vercel@latest
+                vercel --version

Optional (outside this hunk): pin the Node.js runtime so CLI behavior isn’t affected by a runner image update.

- name: Setup Node
  uses: actions/setup-node@v4
  with:
    node-version: '20'  # or your chosen LTS

.github/workflows/deploy_production.yml (1)

29-29: Pin Vercel CLI version in production workflow

I ran a quick search across your workflows and confirmed that both deploy_production.yml (line 29) and deploy_preview.yml (line 31) currently install the Vercel CLI with @latest. For production, we should source a controlled version instead of floating on latest:

• File: .github/workflows/deploy_production.yml
Replace:

-              run: npm install --global vercel@latest
+              run: |
+                VERSION="${{ vars.VERCEL_CLI_VERSION }}"
+                if [ -z "$VERSION" ]; then VERSION="latest"; fi
+                echo "Installing vercel@$VERSION"
+                npm install --global "vercel@$VERSION"
+                vercel --version

This approach:

• Keeps the default behavior (latest) if you haven’t set VERCEL_CLI_VERSION.
• Makes it trivial to pin or roll back by updating a single repo variable.
• Logs the exact version being used for traceability.

Preview can safely remain on @latest (or adopt the same pattern if you prefer consistency).

Optional extra for determinism (both workflows):

- name: Setup Node
  uses: actions/setup-node@v4
  with:
    node-version: '20'  # pin your chosen LTS

Let me know if you need a hand configuring the repo variable or updating the other workflow.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 14e4990 and db50d29.

📒 Files selected for processing (2)

• .github/workflows/deploy_preview.yml (1 hunks)
• .github/workflows/deploy_production.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: deploy-preview