Deployment

Deployment

Branches

• main is the Go implementation and the active development branch.
• python-version preserves the previous Python implementation.

CLI Release

Releases are automated from main. Merging to main creates the next stable semver tag and runs GoReleaser in the same workflow:

v0.2.0
v0.2.1
v0.2.2

Preview tags such as v0.2.0-go.9 are historical only; stable releases use plain semver without the -go.N suffix.

The release workflow builds Darwin, Linux, and Windows archives, publishes a GitHub release, and updates the Homebrew tap when the HOMEBREW_TAP_GITHUB_TOKEN repository secret is configured. Windows artifacts are published as zip archives.

Homebrew Install

brew install vanducng/tap/miudb
brew upgrade vanducng/tap/miudb
miudb version --output json

Documentation Deploy

Documentation deploys from main through GitHub Pages:

cd docs && npm run build   # astro build -> docs/dist/

The docs workflow builds docs/ with withastro/action (custom domain from docs/public/CNAME) and deploys it through actions/deploy-pages.

MCP Release Check

The Homebrew and go install artifacts include the local stdio MCP server; no extra runtime dependencies are required after miudb is on PATH.

Verify before release

Run these checks before cutting a release; the MCP transport check must exit with code 2.

go test ./...
go test ./tests/go -run TestMCPCommandTransportSQLiteFlow -count=1
go build -buildvcs=false -o ./.miu-db/miudb ./cmd/miudb
./.miu-db/miudb mcp serve --transport bad 1>/tmp/miudb-mcp.out 2>/tmp/miudb-mcp.err || test $? -eq 2
test ! -s /tmp/miudb-mcp.out

miudb mcp serve --transport stdio is the supported MCP entry point. Native miudb serve --protocol jsonrpc|ndjson remains for Neovim and custom clients.