pre-release-validation

name	pre-release-validation
description	Run comprehensive pre-release checks: full test suite, E2E tests, coverage verification, CHANGELOG validation, and generated code freshness. Triggers on: before creating a release tag, release preparation.

Pre-Release Validation

Procedure

1. Verify CHANGELOG

Check that CHANGELOG.md has entries under ## [Unreleased]:

sed -n '/^## \[Unreleased\]/,/^## \[v/p' CHANGELOG.md | grep -c "^- "

If no entries, FAIL: "No unreleased changes documented in CHANGELOG.md."

2. Verify generated code is fresh

go generate
git diff --name-only azurecaf/models_generated.go

If there are uncommitted changes, FAIL: "Generated code is stale. Run go generate and commit."

3. Run full test suite

make test_ci 2>&1 | tee /tmp/prerelease-tests.txt

All tests must pass.

4. Run E2E tests

make test_e2e 2>&1 | tee /tmp/prerelease-e2e.txt

All E2E tests must pass.

5. Check coverage

make test_coverage 2>&1 | tee /tmp/prerelease-coverage.txt

Coverage must be >= 95%.

6. Report

## Pre-Release Validation Report

| Check | Status |
|-------|--------|
| CHANGELOG has entries | ✅ / ❌ |
| Generated code fresh | ✅ / ❌ |
| Unit tests | ✅ / ❌ |
| E2E tests | ✅ / ❌ |
| Coverage >= 95% | ✅ (<percentage>%) / ❌ (<percentage>%) |

Overall: READY FOR RELEASE / NOT READY

7. Cleanup

rm -f /tmp/prerelease-*.txt