Bump vercel cli version

[amitsingh-007]

Check if the Pull Request fulfils these requirements

• Does the extension require a version change?

Greptile Summary

This PR bumps the Vercel CLI from 50.25.4 to 53.1.0 by updating the catalog entry in pnpm-workspace.yaml and regenerating the lock file. The lock file changes are consistent with the version bump — all @vercel/* sub-packages are updated, new packages such as @vercel/sandbox, @vercel/oidc, and @vercel/prepare-flags-definitions are introduced as transitive dependencies, and obsolete packages like pip-requirements-js and ohm-js are removed.

Confidence Score: 5/5

This PR is safe to merge — it is a clean dependency version bump with no application code changes.

Only dependency files are modified. The lock file is fully consistent with the catalog change, all integrity hashes are present, and no application logic is touched.

No files require special attention.

_{Reviews (1): Last reviewed commit: "Bump vercel cli version" | Re-trigger Greptile}

[coderabbitai]

Warning

Rate limit exceeded

@amitsingh-007 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 36 minutes and 44 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ 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.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9ce285cd-3547-4334-8d0e-5977949430ae

📥 Commits

Reviewing files that changed from the base of the PR and between 26fa828 and e1d87f9.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• pnpm-workspace.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch f-fix-ci-build

---

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

_{Review rate limit: 0/1 reviews remaining, refill in 36 minutes and 44 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[gemini-code-assist]

Code Review

This pull request updates the vercel package to version 53.1.0, leading to a large-scale update of transitive dependencies in the lockfile. The review feedback correctly identifies a critical Node.js compatibility issue where the new undici dependency requires version 20.18.1+, breaking support for Node.js 18. Additionally, the update introduces a legacy version of js-yaml, creating a duplicate dependency that should be unified with the existing version 4.x to minimize the maintenance surface.

[gemini-code-assist]

The introduction of undici@7.25.0 (via @vercel/sandbox) imposes a Node.js requirement of >= 20.18.1. This contradicts the engines field of the main vercel@53.1.0 package (line 7036), which specifies >= 18. This mismatch breaks compatibility for users on Node.js 18 or older versions of Node.js 20. Consider pinning undici to a compatible 6.x version to maintain broader Node.js support.

[gemini-code-assist]

This update introduces js-yaml@3.14.2 as a dependency for @vercel/backends. Since js-yaml@4.1.1 is already present in the project (e.g., line 9682), this creates a duplicate dependency on a legacy version. Version 3.x is deprecated and has a different security profile. Unifying the js-yaml versions to 4.x is recommended to reduce maintenance surface and bundle size.