Setting the skill. One moment.
24 skills · 112 min
Credited skills
Skill 19 of 24
Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the test_e2e_deploy_release.yml GitHub Actions workflow.
2 minutes · 467 words · 5 sections
Use this skill only when manually running the entire Next.js deployment test suite for a pull request. Treat package validation as a hard gate: never dispatch the workflow until the exact commit’s redirected tarball responds successfully.
Do not use this workflow to sanity-check one deployment test or a focused group of tests. Follow Running Deploy Tests Locally (opens in a new tab) instead:
NEXT_TEST_VERSION=https://vercel-packages.vercel.app/next/commits/<commit-sha>/next pnpm test-deploy <path-to-test>If a request to “run deploy tests” does not explicitly call for the entire suite, prefer the focused local workflow and scope it to the affected tests.
vercel/next.js and workflow
.github/workflows/test_e2e_deploy_release.yml.vercel/next.js. A fork branch cannot
run this secret-bearing workflow; use the repository’s PR adoption process
first when appropriate.Resolve the PR branch and its latest commit from GitHub, not merely from the local checkout:
gh pr view <pr-number> --repo vercel/next.js \
--json number,url,headRefName,headRefOid,isCrossRepositoryIf no PR number was supplied, omit <pr-number> to detect the PR from the
current branch. Stop if isCrossRepository is true. Record headRefName
as the branch and headRefOid as the commit SHA.
Construct the exact package URL:
https://vercel-packages.vercel.app/next/commits/<commit-sha>/nextWait for the package to become downloadable before dispatching anything:
node scripts/wait-for-preview-tarball.mjs --commit-sha <commit-sha>Keep the wait in an ongoing terminal session and poll it so the user still receives progress updates. The helper uses , follows the redirect to Vercel Blob, and only succeeds when the final artifact is available. Do not substitute a check that accepts the initial redirect: that endpoint can redirect even while the blob still returns 404.
Report the PR branch, validated SHA and package URL, workflow run URL, and its current status. Do not wait for the full deployment suite unless the user asks you to monitor it.
$pr-status-triage - Inspect failures if the deployment workflow does not pass.$create-pr - Create or update the internal PR branch before deployment testing.Credited
This skill is installed in vercel/next.js — in use here rather than published from here — so there is no install command for it on this page.
Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the test_e2e_deploy_release.yml GitHub Actions workflow. Use only when asked to run the full deploy test suite or this workflow specifically from an internal vercel/next.js PR branch. Do not use for focused deployment-test sanity checks; run the relevant tests locally with pnpm test-deploy instead. Covers resolving the latest branch SHA, waiting for vercel-packages, preserving default workflow inputs, dispatching the workflow, and verifying the run.
The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.
canary, last pushed 28 August 2026.SKILL.md, not by matching a directory convention. 2 distinct layouts observed: .agents/skills/*/SKILL.md, skills/*/SKILL.md.h1 and no skipped levels:.claude-plugin/marketplace.json by Vercel, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree.HEADIf the helper times out or reports an authorization or build failure, do not
dispatch the workflow. Report the failure and inspect the commit’s
build-and-deploy / upload-preview-tarballs checks if useful.
Resolve the PR again immediately after validation. Compare the current
headRefName and headRefOid with the recorded values. If either changed,
return to step 2 and validate the new commit-specific URL. Never reuse the
old package URL for a moved branch.
Trigger the workflow from the PR branch and pass only nextVersion:
gh workflow run test_e2e_deploy_release.yml \
--repo vercel/next.js \
--ref <pr-branch> \
-f nextVersion=https://vercel-packages.vercel.app/next/commits/<commit-sha>/nextDo not pass any other -f values. Leaving them unspecified preserves the
workflow defaults, including vercelCliVersion: vercel@latest and empty
optional overrides.
Find and verify the newly created run:
gh run list --repo vercel/next.js \
--workflow test_e2e_deploy_release.yml \
--branch <pr-branch> \
--event workflow_dispatch \
--limit 5 \
--json databaseId,url,status,conclusion,headBranch,headSha,displayTitle,createdAtConfirm that the newest matching run has:
headBranch equal to the PR branchheadSha equal to the validated commit SHAdisplayTitle containing the exact commit-specific package URLA race can still move the branch between the final check and dispatch. If the
run’s headSha differs, report the mismatch and do not trigger another run
until the new SHA’s package has been validated.
/vercel/next.js.md, and each skill at its own .md URL.1 file · 253 B
Everything this skill ships beside its prose. All of it is set here, as a subchapter of skill 19.
Everything else published alongside the skill.