Release Management

• You have push permission for tags.
• CI status for current branch is green.
• Version has been agreed and documented.

Core Workflow

1. Prepare:
   • Sync with the agreed release source branch or commit.
   • Ensure no pending uncommitted changes.
2. Validate locally:
   • composer lint:all
   • composer test
   • Confirm docs and examples are in sync with the release content
3. Tag and push:
   • git tag vX.Y.Z
   • git push origin vX.Y.Z
4. Monitor release workflow completion.
5. Verify GitHub release notes and Packagist update.

If the team release source branch is unclear, mark it as Needs clarification rather than assuming develop or master.

Failure Playbook

• Release validation test fails:
  • Fix issue on branch, retag with next patch version if needed.
• Release passes locally but fails in CI:
  • Compare local checks with validate job behavior and workflow permissions.
• Tag format invalid:
  • Use strict vX.Y.Z naming.
• Packagist publish fails:
  • Check repository secrets and rerun release job.

Definition Of Done

• Release tag exists and matches intended version.
• Release workflow completed successfully.
• GitHub release is available and correct.
• Packagist reflects the new version.