Versioning Engine

Map Commit-Scopes to semver bumps via .ags/versioning.yml and version_plan_bump / version_enforce.

What you will learn

Configure bumpRules
version_plan_bump
version_enforce

Prerequisites

Surface

MCP	version_get · version_validate · version_enforce · version_plan_bump
Config	.ags/versioning.yml

What this feature does

Bump rules bind staging categories to major/minor/patch/none. Agents plan bumps before release commits; version_enforce checks package.json vs policy.

Configuration

Wire these surfaces first: .ags/versioning.yml.. Treat them as the contract agents must not invent around.

.ags/versioning.yml yaml

schemaVersion: 1
scheme: semver
packages:
  - name: "@acme/app"
    path: packages/app/package.json
    previousVersion: "1.0.0"
bumpRules:
  file-create: minor
  function-create: minor
  module-wire: minor
  single-change: patch
  single-fix: patch
  breaking-change: major
  milestone-close: none
changelog:
  path: CHANGELOG.md
graphArtifact: docs/version-map/latest.json

How to call it

Call these MCP tools through your AGS / tower-gov host — version_get, version_validate, version_enforce, version_plan_bump.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

version_get
version_plan_bump
Apply version in package.json
version_enforce

MCP: version_plan_bump json

{ "commitScope": "function-create", "packageName": "@acme/app" }

What success looks like

Plan matches bumpRules

version_enforce ok after bump

Common failure modes

Forgot to bump package.json

breaking-change committed as patch

CAP off when enforce expects commit session