[AAASM-2334] 🐛 (release-intent): Disable centralized auto-release (release: true → false)

[Chisanan232]

Description

Every push to python-sdk master since alpha-2 has been silently failing the centralized release workflow with fatal: tag 'v0.0.2' already exists. The workflow auto-bumps version per intent.yaml: level: patch and tries to create a tag that already exists from the alpha-2 cycle's auto-bump.

The operator flow is manual: push v* tag → Release Python SDK builds wheels with the AAASM-2189 protoc fix → publishes via Trusted Publisher OIDC. The centralized auto-release is redundant AND broken.

Fix

release: true → release: false in .github/tag_and_release/intent.yaml.

Related

• Jira: AAASM-2334
• Discovery: python-sdk release workflow run 26737994023 (alpha-3 cycle)

— Claude Code

[Chisanan232]

Claude Code review — AAASM-2334

CI state

7 SUCCESS + 6 SKIPPED, 0 failures — mergeable=MERGEABLE, mergeStateStatus=CLEAN. Same intentional-skip pattern as previous python-sdk intent-config PRs (PR #66, etc.) — the centralized release validation steps skip on PR context.

Scope vs. AC

AC	Verified	Status
intent.yaml release: true → release: false	single 1-line edit	✅
Comment / commit-message explains the failure mode (tag collision)	yes — commit body documents run 26737994023 + the fatal: tag 'v0.0.2' already exists evidence	✅
Release Python SDK workflow (tag-triggered, with AAASM-2189 protoc fix) continues to handle manual-tag releases	yes — release: false only disables the centralized auto-release; tag-push trigger on Release Python SDK is independent	✅
actionlint clean (no schema regression in intent.yaml)	(intent.yaml is not a workflow file; doesn't run through actionlint but the YAML is valid)	✅

What this fixes

Every master push since alpha-2 has been silently failing the centralized release workflow because it auto-bumps from the current pyproject version (0.0.1a2 → 0.0.2, then 0.0.2 → 0.0.3, etc., per level: patch) and tries to create a tag that conflicts with a prior auto-bump tag. Hard to spot because nothing user-facing breaks — just a red release workflow run in the history.

After this PR merges:

• Master pushes do NOT trigger the centralized release workflow
• Operator pushes a v* tag manually → Release Python SDK builds wheels with the AAASM-2189 fix → publishes to PyPI via Trusted Publisher OIDC
• Releases are explicitly operator-initiated; no surprise auto-bumps

Verdict

Ready for human approval and merge. Smallest possible fix for a class of failures that had been silently accumulating since alpha-2.

— Claude Code (Opus 4.7, 1M context)