Skip to content

chore: add capability-scoped release automation#36

Merged
GangGreenTemperTatum merged 1 commit into
mainfrom
ads/cap-991-use-release-versions-for-capabilities-release-notes
Jun 5, 2026
Merged

chore: add capability-scoped release automation#36
GangGreenTemperTatum merged 1 commit into
mainfrom
ads/cap-991-use-release-versions-for-capabilities-release-notes

Conversation

@GangGreenTemperTatum
Copy link
Copy Markdown
Contributor

@GangGreenTemperTatum GangGreenTemperTatum commented Jun 5, 2026

Summary

  • add a planner that detects capability.yaml version bumps and maps them to capability-scoped GitHub release tags
  • create GitHub Releases after successful main-branch capability sync using GitHub generated release notes
  • add tests for version bump detection, unchanged manifests, previous tag selection, and duplicate tag skips

Release convention

Tags use capability/<capability-name>/v<manifest-version>, for example capability/ai-red-teaming/v1.3.7. Releases are created with --generate-notes and --notes-start-tag when a prior tag for that same capability exists.

Validation

  • uv run pytest tests/test_capability_release_plan.py -q
  • pre-commit run --files .github/workflows/sync.yml scripts/capability_release_plan.py tests/test_capability_release_plan.py
  • just validate (passed with existing capability check warnings only)

@GangGreenTemperTatum GangGreenTemperTatum changed the title Add capability-scoped release automation chore: add capability-scoped release automation Jun 5, 2026
@GangGreenTemperTatum GangGreenTemperTatum merged commit bdd709b into main Jun 5, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant