skills.rest
vercel
vercelOFFICIAL
Explore all skills by this author →
Website𝕏@vercelGitHub

deploy-release-test

Validate and trigger the Next.js deploy release test suite via GitHub Actions.

142k|31.8k|Updated Oct 5, 2016
Search Tags:#next.js#deployment testing#ci/CD#GitHub actions#workflow dispatch#preview package#vercel-packages
One-click install
npx skills add https://github.com/vercel/next.js --skill deploy-release-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deploy-release-test
Source: https://github.com/vercel/next.js/tree/main/.agents/skills/deploy-release-test
Command: npx skills add https://github.com/vercel/next.js --skill deploy-release-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually running the full Next.js deployment test suite for a pull request requires coordinating package validation, branch resolution, and workflow dispatch without breaking secret-bearing CI constraints. This Skill automates that orchestration so contributors do not dispatch a workflow against an unavailable or stale preview package.

Core Features & Use Cases

  • Commit-Specific Package Validation: Polls the vercel-packages tarball endpoint until the exact commit's artifact is downloadable before dispatching anything.
  • Workflow Dispatch with Default Inputs: Triggers test_e2e_deploy_release.yml from the PR branch while preserving default workflow inputs such as vercelCliVersion.
  • Run Verification: Confirms the newly created GitHub Actions run matches the validated branch, SHA, and package URL.
  • Use Case: A Vercel engineer needs to run the entire deployment test suite against a PR branch in vercel/next.js. Use this Skill to validate the commit-specific preview package, dispatch the workflow, and verify the resulting run.

Quick Start

Use the deploy-release-test skill to validate the latest commit package for PR 12345 in vercel/next.js and trigger the full deployment test suite.

Frequently Asked Questions about deploy-release-test

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

FAQPage Schema
How do I run the full Next.js deploy release test suite for a PR?▼

Resolve the PR branch and SHA with `gh pr view`, validate the commit-specific package via `scripts/wait-for-preview-tarball.mjs`, then dispatch `test_e2e_deploy_release.yml` using `gh workflow run` with only the `nextVersion` input. Verify the run with `gh run list`.

What is the difference between running deploy tests locally and via this workflow?▼

Local runs use `NEXT_TEST_VERSION` with `pnpm test-deploy <path-to-test>` for focused sanity checks. This Skill runs the entire deployment suite through GitHub Actions and requires the PR branch to live in `vercel/next.js`.

Can this workflow run on a fork PR branch?▼

No. The workflow carries secrets and only runs on branches that exist in the `vercel/next.js` repository. Fork branches must be adopted through the repository's PR adoption process first.

Why does the workflow dispatch fail after a redirect check passes?▼

The vercel-packages endpoint can redirect to Vercel Blob even when the blob returns 404. The helper script follows the redirect and only succeeds when the final artifact responds successfully, so a passing redirect alone is not sufficient.

When should I not use the deploy-release-test skill?▼

Do not use it for focused deployment-test sanity checks. Run the relevant tests locally with `NEXT_TEST_VERSION=<url> pnpm test-deploy <path-to-test>` instead, scoping to the affected tests.

Related Skills

Explore More Software Engineering Skills→
dain-agencydain-agency

publish-mcp-server

Automate npm publishing and Vercel deployment for @dain-os/mcp-server.

Official
Advanced
sensei-hackersensei-hacker
4

check-builds

Check GitHub Actions CI build status for pull requests and workflow runs.

Community
Intermediate
BedaBeda-GrowthBedaBeda-Growth

jules-e2e-fallback

Diagnose failing Jules E2E branches, patch code, and re-dispatch Playwright runs.

Official
Advanced
blaxel-aiblaxel-ai
25

run-e2e

Run end-to-end tests against a sandbox image to validate the sandbox-api binary.

Official
Advanced