Release
Cut a vercel-plugin release by running parallel quality gates, bumping semver in plugin.json, rebuilding artifacts, and pushing a versioned commit.
Install
npx skills add https://github.com/vercel-labs/vercel-plugin --skill releaseWhat is this skill?
- Parallel pre-flight: bun typecheck, bun test, and bun run validate—stop on any failure
- Semver bump table: patch vs minor vs major tied to hooks API and skill-map breaks
- Single version source of truth in .plugin/plugin.json
- bun run build compiles hooks via tsup and regenerates generated/skill-manifest.json
- Standard git add -A, versioned commit message, and push to complete release
Adoption & trust: 211 installs on skills.sh; 187 GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Release Skillsjimliu/baoyu-skills
Changelog Automationwshobson/agents
Msstore Cligithub/awesome-copilot
Changelog Generatorcomposiohq/awesome-claude-skills
Shopify App Store Reviewshopify/shopify-ai-toolkit
Shipping And Launchaddyosmani/agent-skills
Journey fit
Primary fit
Ship launch is the moment a plugin version becomes consumable; this skill encodes the full cut-over from green gates to git push. Launch subphase fits semver bump, manifest regeneration, and distribution via git—not day-to-day feature coding.
Common Questions / FAQ
Is Release safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Release
# 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 # hooks (tsup) + manifest ``` This compiles `hooks/src/*.mts` → `hooks/*.mjs` and regenerates `generated/skill-manifest.json`. ### 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` succeeded - [ ] commit includes all changes - [ ] pushed to main