release
This Claude Code skill automates releasing new versions of the Vellum Assistant by dispatching GitHub Actions workflows. It accepts an optional argument specifying the version bump type (patch, minor, or major, defaulting to patch), validates the input, triggers the Release workflow on the main branch, and provides confirmation that the automated pipeline has started, which handles version bumping, package publishing, and macOS notarization over approximately 15-20 minutes.
git clone --depth 1 https://github.com/vellum-ai/vellum-assistant /tmp/release && cp -r /tmp/release/.claude/skills/release ~/.claude/skills/releaseSKILL.md
Cut a new release by triggering the Release workflow via GitHub Actions workflow dispatch.
The user may pass `$ARGUMENTS` as the bump type: `patch`, `minor`, or `major`. If not provided, default to `patch`.
## Steps
### 1. Pull latest main
```bash
git checkout main && git pull
```
### 2. Determine the bump type
If the user provided `$ARGUMENTS`, treat it as the bump type (`patch`, `minor`, or `major`). Otherwise default to `patch`.
Validate + show what you're about to do and ask for confirmation before proceeding:
```bash
BUMP_TYPE="${ARGUMENTS:-patch}"
case "$BUMP_TYPE" in
patch|minor|major) ;;
*) echo "Invalid bump type: $BUMP_TYPE (expected patch|minor|major)"; exit 1 ;;
esac
echo "About to trigger a $BUMP_TYPE release bump"
```
### 3. Trigger the Release workflow
```bash
gh workflow run release.yml \
--repo vellum-ai/vellum-assistant \
--ref main \
--field bump=<patch|minor|major>
```
This triggers the unified Release workflow which automatically handles:
- Version bumping across all packages
- Creating a release branch, PR, and merging it
- Tagging the release
- Publishing npm packages
- Building, signing, notarizing, and publishing the macOS DMG
- Creating GitHub Releases on `vellum-ai/vellum-assistant`
- Updating the `vellum-assistant-platform` dependency
### 4. Verify the workflow started
```bash
gh run list --repo vellum-ai/vellum-assistant --workflow="Release" --limit 1
```
Confirm the workflow was triggered.
### 5. Report
Output:
- The version number (from the workflow output)
- A link to the running workflow
- Remind the user that the full release pipeline takes ~15-20 minutes and will auto-publish everything when done>
>
>
Check Vellum Assistant architecture and package boundaries. Use when editing imports, moving code, adding endpoints, touching assistant/gateway/client/skill boundaries, or reviewing architecture-sensitive changes.
Review Vellum Assistant code changes for correctness, repo-specific quality rules, security risks, and missing validation. Use when reviewing diffs, preparing a PR, finishing implementation work, or when the user asks for a code review, quality pass, or pre-merge check in this repository.
Guide Vellum Assistant feature flag changes and rollout hygiene. Use when adding, editing, reviewing, or documenting assistant feature flags, rollout-gated behavior, or platform flag follow-up work.
Validate Vellum Assistant database and workspace migrations. Use when adding, editing, reviewing, or testing migrations, release-note migrations, persisted schemas, workspace file formats, or data backfills.
Prepare Vellum Assistant branches for review by checking git hygiene, PR scope, tests, docs, migrations, Linear linking, and companion repo needs. Use before creating a pull request, splitting work into PRs, or asking whether a branch is ready.