Files
servers/.github
Adam Jones f5c517a037 Fix create-release job condition to properly handle skipped publish jobs
The previous condition had two issues:
1. `always()` was incorrectly placed after the changes_made check, making it ineffective
2. The condition was overly verbose with explicit OR checks for all combinations

This fix:
- Moves `always()` to the beginning so the condition evaluates even when publish jobs are skipped
- Simplifies the logic to check if at least one publish job succeeded
- Adds documentation explaining why always() is needed

Without `always()` at the start, the job would never run when dependencies are skipped,
and the result checks would never be evaluated.
2025-09-18 14:48:07 +00:00
..