Versioning Simulated 3 MCP tools

Versioning Engine

Semantic version graphs, bump rules, and changelog animation.

How you use it

Keep bump rules in .ags/versioning.yml. Before release: version_plan_bump → apply → version_enforce. Do not hand-edit version numbers against the graph.

Token savings

Removes debate loops about “is this minor or patch?” Agents follow the map; humans review the plan once.

Consistency

Every release bump is derived from Commit-Scopes — tags and notes stay aligned with what actually shipped.

In action

Versioning

Change set

feat + fix land under governed scopes.

Plan bump

Tag

Notes

Interactive demo

2.4.1 patch

Changelog

2.4.1 — Baseline release

Semver rules

2.4.1 → 2.4.2

Bugfix, docs, test-only

2.4.2 → 2.5.0

New engine showcase, backward compatible

2.5.0 → 3.0.0

Breaking .ags schema or commit trailer

Version time-travel Idle

Scrub playback to preview semver milestones. Bumps append animated changelog lines.

Simulated behavior only — does not execute proprietary AGS engine code.

Diagram

Example usage

# .ags/versioning.yml
scheme: semver
bumpRules:
  feat: minor
  fix: patch
  breaking: major

# MCP: version_enforce
{}

Docs →

version_get
version_plan_bump
version_enforce