AILANG Release Manager

AILANG Release Manager

Create a complete AILANG release with version bump, changelog update, git tag, and CI/CD verification.

Quick Start

Most common usage:

# User says: "Ready to release v0.3.14"
# This skill will:
# 1. Run pre-release checks (tests, lint, file sizes)
# 2. Update version in docs
# 3. Create git tag
# 4. Push to trigger CI/CD
# 5. Verify release artifacts
# 6. Broadcast release notification with changelog

When to Use This Skill

Invoke this skill when:

• User says "ready to release", "create release", "publish release"
• User mentions a specific version number (e.g., "v0.3.14")
• User asks about release process or workflow
• After completing a sprint and code is ready to ship

Available Scripts

scripts/pre_release_checks.sh

Run all pre-release verification checks before making any changes.

Usage:

.claude/skills/release-manager/scripts/pre_release_checks.sh

What it checks:

1. Test suite passes (make test)
2. Linting passes (make lint)
3. No files exceed 800 lines (make check-file-sizes)

Output:

Running pre-release checks...

1/3 Running test suite...
  ✓ Tests passed

2/3 Running linter...
  ✓ Linting passed

3/3 Checking file sizes...
  ✓ File sizes OK (all files ≤800 lines)

✓ All pre-release checks passed!
Ready to proceed with release.

Exit codes:

• 0 - All checks passed
• 1 - One or more checks failed (see logs in /tmp/pre_release_*.log)

scripts/check_implemented_docs.sh <version>

Verify all implemented design docs are documented in CHANGELOG.

Usage:

.claude/skills/release-manager/scripts/check_implemented_docs.sh 0.5.10

What it checks:

1. Finds all design docs in design_docs/implemented/vX_Y_Z/
2. Verifies each feature doc is referenced in CHANGELOG.md
3. Skips sprint plans and analysis docs (implementation artifacts)

Exit codes:

• 0 - All feature docs are in CHANGELOG
• 1 - Some docs are missing from CHANGELOG

scripts/post_release_checks.sh <version>

Verify release was created successfully on GitHub.

Usage:

.claude/skills/release-manager/scripts/post_release_checks.sh 0.3.14

What it checks:

1. Git tag exists (git tag -l v0.3.14)
2. GitHub release exists (gh release view v0.3.14)
3. All platform binaries present (Darwin x64/ARM64, Linux, Windows)
4. Latest CI run passed

scripts/update_version_constants.sh <version>

Update website version constants to the new release version.

Usage:

.claude/skills/release-manager/scripts/update_version_constants.sh 0.5.7

What it updates:

• docs/src/constants/version.js - STABLE_RELEASE and ACTIVE_PROMPT

Output:

Updating docs/src/constants/version.js...
  STABLE_RELEASE: v0.5.6 → v0.5.7
  ACTIVE_PROMPT: v0.5.2 → v0.5.2
✓ Updated docs/src/constants/version.js

scripts/collect_closable_issues.sh <version> [--close] [--json]

Find GitHub issues that can be closed with this release.

Uses ailang messages GitHub integration for efficient issue discovery.

Usage:

.claude/skills/release-manager/scripts/collect_closable_issues.sh 0.5.9
.claude/skills/release-manager/scripts/collect_closable_issues.sh 0.5.9 --close
.claude/skills/release-manager/scripts/collect_closable_issues.sh 0.5.9 --json

What it scans:

1. GitHub sync - Runs ailang messages import-github to sync latest issues
2. ailang messages - Queries local message database for GitHub-linked issues
3. Commits since last tag for issue references (Fixes #123, Closes #456, etc.)
4. CHANGELOG.md entry for the version
5. Design docs in design_docs/implemented/vX_Y_Z/ and design_docs/planned/vX_Y_Z/
6. Keyword matching between message content and CHANGELOG

Options:

• --close - Actually close the issues via gh issue close
• --json - Output JSON format for including in release notes

For output examples, see resources/script_examples.md.

Note: When closing issues (--close), the script also marks the corresponding ailang messages as read via ailang messages ack.

Deduplication: ailang messages import-github checks existing issues by number before importing - issues are never duplicated.

Alternative: Auto-close via commits - Instead of using --close, include Fixes #123 in the release commit message. GitHub will auto-close issues when the commit is merged to the default branch.

scripts/close_issues_with_references.sh <version> <issue> [section]

Close a GitHub issue with proper release references (URLs, commits, design docs).

Usage:

.claude/skills/release-manager/scripts/close_issues_with_references.sh 0.5.10 29
.claude/skills/release-manager/scripts/close_issues_with_references.sh 0.5.10 29 'M-STRING-CONVERT'

What it does:

1. Gets release URL and commit hash for the version
2. Extracts relevant CHANGELOG section (auto-detects or uses provided section name)
3. Finds related design doc if exists
4. Generates a comprehensive closing comment with all references
5. Prompts for confirmation, then closes the issue

For more details: See resources/issue_closure_guide.md

scripts/broadcast_release.sh <version> [--include-issues]

Broadcast release notification with changelog to all projects.

Usage:

.claude/skills/release-manager/scripts/broadcast_release.sh 0.4.5
.claude/skills/release-manager/scripts/broadcast_release.sh 0.4.5 --include-issues

Options:

• --include-issues - Include list of closed/closable GitHub issues in the notification

What it does:

1. Extracts the changelog entry for the given version
2. Optionally collects related GitHub issues (using collect_closable_issues.sh)
3. Creates a structured release notification message with changelog and closed issues
4. Broadcasts to the user inbox (global notification point)
5. Projects receive notification when they check their inbox

Release Workflow

1. Pre-Release Verification (CRITICAL)

Run checks BEFORE making any changes:

.claude/skills/release-manager/scripts/pre_release_checks.sh

If checks fail:

• Tests failing → Fix tests first
• Linting failing → Run make fmt or fix issues
• File sizes failing → Use codebase-organizer agent to split large files
• DO NOT proceed until all checks pass

2. Verify Implemented Design Docs (CRITICAL)

Check that all implemented features are documented:

.claude/skills/release-manager/scripts/check_implemented_docs.sh X.X.X

This checks design_docs/implemented/vX_Y_Z/ against CHANGELOG:

• Every feature doc should have a CHANGELOG entry
• Sprint plans and analysis docs are skipped (implementation artifacts)
• If docs are missing from CHANGELOG, add entries before proceeding

If docs are missing:

• Read each missing doc to understand the feature
• Add appropriate entry to CHANGELOG.md under the version header
• Include: problem, solution, files changed, design doc link

3. Update Version in Documentation

Run the version update script:

.claude/skills/release-manager/scripts/update_version_constants.sh X.X.X

Also update these files manually:

• CHANGELOG.md: Change ## [Unreleased] to ## [vX.X.X] - YYYY-MM-DD
• std/VERSION: Change to vX.X.X (used by stdlib resolver for version checking)

The script automatically updates:

• docs/src/constants/version.js - Website STABLE_RELEASE and ACTIVE_PROMPT

4. Post-Update Verification (CRITICAL)

Run checks AGAIN after documentation changes:

make test
make lint

If either fails, fix before committing.

4. Commit Changes

git add CHANGELOG.md std/VERSION docs/src/constants/version.js
git commit -m "Release vX.X.X"

5. Create and Push Git Tag

git tag -a vX.X.X -m "Release vX.X.X"
git push origin vX.X.X

6. Push Commit

git push

7. Monitor CI/CD

# Check recent runs
gh run list --limit 3

# Watch for completion (typically 2-3 minutes)
gh run watch

8. Collect and Close Related Issues

Find issues that can be closed with this release:

.claude/skills/release-manager/scripts/collect_closable_issues.sh X.X.X

Review the suggested issues, then close them:

.claude/skills/release-manager/scripts/collect_closable_issues.sh X.X.X --close

The script scans commits, CHANGELOG, and design docs for issue references, and matches open issues against CHANGELOG keywords.

9. Verify Release

Use the verification script:

.claude/skills/release-manager/scripts/post_release_checks.sh X.X.X

Or manually:

gh release view vX.X.X

Expected binaries:

• ailang-darwin-amd64.tar.gz (macOS Intel)
• ailang-darwin-arm64.tar.gz (macOS Apple Silicon)
• ailang-linux-amd64.tar.gz (Linux)
• ailang-windows-amd64.zip (Windows)

10. Broadcast Release Notification

Notify all projects about the new release:

.claude/skills/release-manager/scripts/broadcast_release.sh X.X.X

This extracts the changelog entry for the version and broadcasts it to the user inbox. External projects will see the notification when they check their inbox.

What gets broadcast:

• Version number and release date
• Full changelog section (Added, Changed, Fixed, etc.)
• Link to GitHub release page

11. Handle CI Failures

If CI fails after push:

# Check logs
gh run list --workflow=CI --limit 3
gh run view <run-id> --log-failed

# Fix issues
# Commit fixes
git commit -m "Fix CI: <issue>"
git push

12. Summary

Show user:

• ✓ Version vX.X.X released
• ✓ Git tag created
• ✓ Release URL: https://github.com/sunholo-data/ailang/releases/tag/vX.X.X
• ✓ CI workflow status
• ✓ Related GitHub issues closed (if any)
• ✓ Release notification broadcast to projects
• Next step: Run post-release skill to update benchmarks and dashboard

Resources

Release Checklist

See resources/release_checklist.md for complete step-by-step checklist.

Issue Closure Guide

See resources/issue_closure_guide.md for how to properly close GitHub issues with:

• Release URLs and commit references
• CHANGELOG excerpts
• Design doc links
• Best practices for closing comments

Prerequisites

• Working directory must be clean (no uncommitted changes)
• Current branch should be dev or main
• All tests must pass (make test)
• All linting must pass (make lint)
• No files exceed 800 lines (make check-file-sizes)

Version Format

Semantic versioning: MAJOR.MINOR.PATCH

• Examples: 0.0.9, 0.1.0, 1.0.0

Common Issues

Tests Fail Before Release

Solution: Fix tests first, don't skip this step.

Linting Fails

Solution: Run make fmt to auto-format, or fix manually.

File Size Check Fails

Solution: Use codebase-organizer agent to split large files before releasing.

CI Fails After Push

Solution: Check logs with gh run view <run-id> --log-failed, fix, commit, push again.

Release Missing Binaries

Solution: CI workflow may still be running. Wait 2-3 minutes and check again.

Progressive Disclosure

This skill loads information progressively:

1. Always loaded: This SKILL.md file (YAML frontmatter + workflow overview)
2. Execute as needed: Scripts in scripts/ directory (validation, verification)
3. Load on demand: resources/release_checklist.md (detailed checklist)

Scripts execute without loading into context window, saving tokens while providing automation.

Notes

• This skill follows Anthropic's Agent Skills specification (Oct 2025)
• Scripts handle verification automatically
• Always run pre-release checks BEFORE making changes
• Always run post-update checks AFTER documentation changes
• Use post-release skill after successful release for benchmarks and dashboard