Release Engine

Plan and enforce release artifacts, tags, and notes against .ags/release.yml.

What you will learn

• release_plan
• release_enforce
• Attach changelog evidence

Prerequisites

• Versioning Engine

Surface

What this feature does

Release Engine validates tags, artifacts, and changelog sections required by versioning policy before a release is considered legal.

How to call it

Call these MCP tools through your AGS / tower-gov host — release_get, release_validate, release_enforce, release_plan.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

1. version_enforce
2. release_plan
3. Create tag/notes/artifacts
4. release_enforce

{ "packageName": "@acme/app", "version": "1.1.0" }

What success looks like

release_enforce ok

Notes + tag consistent

Common failure modes

Tag without changelog section

Artifact path missing

Version mismatch vs version_enforce

Related reference

• Versioning
• Deployment