bc-mcp-release

bc-mcp release runbook

Release business-central-mcp to npm. The package is configured for manual publish via prepublishOnly (typecheck + build); the rest is gated by you to keep destructive operations safe.

This is a runbook, not an automated tool. Walk the user through each step, pausing on anything destructive (version bump, publish, tag push) for explicit confirmation. Releases are irreversible — npm allows unpublish only within 72 hours of publish, and only if no other package depends on the exact version.

Preflight checklist

Run these before suggesting a version bump. If any fail, stop and surface the failure — don't paper over it.

cd U:/Git/bc-mcp        # or wherever the repo lives

# Working tree clean?
git status --short          # expect empty
git rev-parse --abbrev-ref HEAD   # expect master

# Up-to-date with origin?
git fetch origin
git status -sb              # expect "## master...origin/master" with no behind/ahead

# All tests pass?
npm run typecheck           # tsc --noEmit, expect exit 0
npm test                    # unit + protocol, expect green
npm run test:integration    # against live BC, expect green (skip if no BC available, but flag the skip)

# CHANGELOG up-to-date?
grep -q "^## \[Unreleased\]" CHANGELOG.md && echo "OK: [Unreleased] section exists"
# Inspect the [Unreleased] section — it should describe what's about to ship.

If integration tests can't run (no live BC), explicitly tell the user "integration tests skipped — running CI to compensate". CI will run unit + protocol on Node 20/22/24 against the master branch via .github/workflows/ci.yml.

Step 1: Pick the version

Read package.json to see the current version. Compare against published versions on npm:

npm view business-central-mcp versions --json

Decide the bump per semver:

Change kind	pre-1.0 (0.x.y)	post-1.0 (x.y.z)
Bug fix only	0.x.y patch	x.y.z patch
New feature, backwards-compatible	0.x.0 minor	x.y.0 minor
Breaking change to public API	0.x.0 minor (allowed pre-1.0)	x.0.0 major