deployments-cicd

Guides Vercel deployments, promotions, rollbacks, and CI/CD pipeline configuration.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/sharad07072007/paras --skill deployments-cicd-sharad07072007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployments-cicd
Source: https://github.com/sharad07072007/paras/tree/main/.agents/plugins/vercel/skills/deployments-cicd
Command: npx skills add https://github.com/sharad07072007/paras --skill deployments-cicd-sharad07072007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying to Vercel through custom CI/CD pipelines involves many moving parts: prebuilt builds, environment variables, tokens, promotions, and rollbacks. This Skill provides expert guidance so you configure these workflows correctly the first time and avoid common build and deployment errors. ## Core Features & Use Cases - Deployment Command Guidance: Covers preview deploys, production deploys, vercel build with --prebuilt, vercel promote, vercel rollback, and vercel inspect. - CI/CD Pipeline Templates: Ready-to-use workflow configurations for GitHub Actions, GitLab CI, and Bitbucket Pipelines, including PR preview deployments and promote-after-test patterns. - Troubleshooting & Best Practices: A build error reference table, deployment strategy matrix, and structured deploy result reporting. - Use Case: You want every pull request to produce a preview URL and automatically promote to production after E2E tests pass. This Skill walks you through the exact GitHub Actions workflow with the correct tokens, flags, and commands. ## Quick Start Ask the assistant to set up a GitHub Actions workflow that builds and deploys your project to Vercel production on every push to main.

Frequently Asked Questions about deployments-cicd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy to Vercel from GitHub Actions?

Install the Vercel CLI in your workflow, then run vercel pull, vercel build --prod, and vercel deploy --prebuilt --prod with --token set to your VERCEL_TOKEN secret. You also need VERCEL_ORG_ID and VERCEL_PROJECT_ID configured as CI secrets.

What is the difference between vercel promote and vercel deploy --prod?

vercel promote instantly re-points the production alias to an existing preview deployment without rebuilding. vercel deploy --prod creates a brand new production deployment, which takes longer but produces a fresh build artifact.

When should I use vercel deploy --prebuilt?

Use --prebuilt in custom CI pipelines where you control the build step with vercel build, want CI-level build caching, or need to run tests between the build and deploy stages. It deploys only the build output without a remote build.

Does Vercel OIDC federation replace VERCEL_TOKEN in CI pipelines?

No. OIDC federation lets deployed Vercel functions authenticate to external services like AWS or GCP at runtime without static secrets. All CLI commands in CI such as vercel pull, build, and deploy still require --token with VERCEL_TOKEN.

How do I roll back a Vercel production deployment?

Run vercel rollback to revert to the previous production deployment, or vercel rollback <deployment-url-or-id> to target a specific deployment. This re-points the production alias without triggering a rebuild.

Why does my Vercel build fail with ERR_PNPM_OUTDATED_LOCKFILE?

This error means your pnpm lockfile does not match package.json. Run pnpm install locally to regenerate the lockfile, commit it, and push again so the CI build uses consistent dependency versions.