jdx c6a35e2d7d chore(ci): use !cancelled() instead of always() for final job (#460) ... ## Summary - Combined with the workflow's `cancel-in-progress` group, `if: always()` overrides cancellation and runs the `final` aggregator even on superseded commits. - `!cancelled()` still runs on upstream success or failure but skips when the workflow is cancelled — saves a runner and avoids confusing error annotations on already-superseded shas. - Caught by Cursor Bugbot on a sibling repo (endevco/pitchfork#413). Same `final`-aggregator pattern + `cancel-in-progress: true` here, so the same fix applies. ## Test plan - [ ] CI passes on this PR 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Low risk CI-only change that just adjusts when the `final` job runs; main risk is slightly different status reporting when runs are cancelled. > > **Overview** > Updates the GitHub Actions `final` aggregator job to use `if: ${{ !cancelled() }}` instead of `always()`, so it still runs for upstream success/failure but **does not** run for cancelled workflows (e.g., superseded runs under `cancel-in-progress`). > > Adds clarifying comments to document why cancellation should skip the aggregator to avoid wasting runners and producing noise on cancelled commits. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 4c62d5f2f1. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY --> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-03 10:27:10 -05:00
..
linters	feat: support windows (#122)	2024-09-25 21:27:52 +00:00
workflows	chore(ci): use !cancelled() instead of always() for final job (#460)	2026-05-03 10:27:10 -05:00
renovate.json	feat: use autofix.ci to auto-update dist/ on all PRs	2025-10-31 09:43:48 -05:00