mcp-server-flipt: Skill for Claude Code

Release a package

Releases one package per invocation. Arguments (ask if missing): which package (v1 or v2) and the bump (patch | minor | major | explicit X.Y.Z).

	v1	v2
npm package	@flipt-io/mcp-server-flipt	@flipt-io/mcp-server-flipt-v2
directory	packages/mcp-server-flipt	packages/mcp-server-flipt-v2
git tag	vX.Y.Z	[email protected]
docker image	ghcr.io/flipt-io/mcp-server-flipt	ghcr.io/flipt-io/mcp-server-flipt-v2

Tags drive .github/workflows/publish.yml (npm + ghcr, each image also tagged :latest).

CRITICAL — tag scheme: a vX.Y.Z tag ALWAYS publishes the v1 package, regardless of what was bumped. Never create a v* tag for a v2 release, and never let pnpm version auto-tag (its default tag is v*). Always pass --no-git-tag-version and create the tag by hand.

Procedure

1. Preflight

git switch main && git pull --ff-only
git status --short          # must be clean; abort if not
pnpm install
pnpm -r check && pnpm lint && pnpm -r test && pnpm -r build

All gates must pass before bumping. Also confirm CI is green on origin/main (gh run list --branch main --limit 3). If releasing a fix that just merged, make sure it's actually in main.

2. Bump

Run inside the package directory (the version lifecycle script regenerates src/version.ts and git adds it — a test fails if it drifts, so never edit version fields by hand):

cd packages/<dir>
pnpm version <patch|minor|major|X.Y.Z> --no-git-tag-version
cd ../..

Confirm packages/<dir>/src/version.ts matches the new package.json version and both are staged/modified. Set NEW_VERSION from the package.json.

3. Commit and tag

git add packages/<dir>/package.json packages/<dir>/src/version.ts
# v1:
git commit -m "chore(release): mcp-server-flipt v${NEW_VERSION}"
git tag "v${NEW_VERSION}"
# v2:
git commit -m "chore(release): mcp-server-flipt-v2 ${NEW_VERSION}"
git tag "mcp-server-flipt-v2@${NEW_VERSION}"