---
name: release
description: Release vercel-plugin — run gates, bump version, generate artifacts, commit, and push. Use when asked to "release", "ship", "bump and push", or "cut a release".
title: release
canonical_url: https://skilld.dev/gh/vercel/vercel-plugin/release
last_updated: 2026-10-08T16:13:25.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install vercel/vercel-plugin/release`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/release`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/vercel/vercel-plugin/release) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/release`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/release --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/release --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Release

End-to-end release workflow for vercel-plugin.

## Workflow

### 1. Pre-flight checks

Run all gates in parallel:

```bash
bun run typecheck          # tsc --noEmit on hooks/src
bun test                   # all test files
bun run validate           # skill frontmatter + manifest integrity
```

**Stop if any gate fails.** Fix issues before proceeding.

### 2. Determine version bump

Read the current version from `.plugin/plugin.json`. Ask the user which semver component to bump if not specified:

| Bump  | When                                      |
|-------|-------------------------------------------|
| patch | Bug fixes, test/fixture updates, docs     |
| minor | New skills, new hooks, new features       |
| major | Breaking changes to hook API or skill map |

Default to **patch** if the user says "release" without specifying.

### 3. Bump version

Update the `version` field in `.plugin/plugin.json`. This is the **only** version source of truth.

### 4. Rebuild generated artifacts

```bash
bun run build:all          # hooks (tsup) + manifest
```

This merges upstream skills with their overlays, compiles `hooks/src/*.mts` → `hooks/*.mjs`, and resolves agent/command templates. Skill metadata is read directly from `SKILL.md` files.

### 5. Stage, commit, and push

```bash
git add -A
git commit -m "<summary>; bump to <new-version>"
git push
```

Commit message style: match existing convention — descriptive summary followed by `; bump to X.Y.Z` (see git log for examples).

The pre-commit hook will re-run typecheck and recompile hooks automatically. If it fails, fix the issue and create a **new** commit (never amend).

## Version source of truth

`.plugin/plugin.json` — the `version` field. There is no `package.json` version to sync.

## Checklist (copy into your reasoning)

- [ ] typecheck passes
- [ ] tests pass
- [ ] validate passes
- [ ] `.plugin/plugin.json` version bumped
- [ ] `bun run build:all` succeeded
- [ ] commit includes all changes
- [ ] pushed to main
