Skip to content

Avoid duplicate release test runs - #78

Merged
blessdyb merged 1 commit into
mainfrom
fix/release-check-dedupe
Nov 4, 2026
Merged

blessdyb merged 1 commit into
mainfrom
fix/release-check-dedupe

Conversation

@blessdyb

@blessdyb blessdyb commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Summary

  • replace Release's duplicate newest-Xcode test run with an exact-commit evidence gate
  • require an open or merged PR targeting main at the checked-out tag SHA
  • require the latest successful oldest/newest Xcode, site, change-detection, Swift/Python/Actions CodeQL, and aggregate CodeQL checks from trusted GitHub apps
  • retain release signing, notarization, Gatekeeper, checksums, publication, and Homebrew validation unchanged
  • document that CI owns tests and Release consumes their exact-SHA evidence

Why

Flowlight 0.16.11 commit 605d45e1 ran the full suite in CI's newest-Xcode job and then ran the same xcodebuild test command again in the Release dry run. The duplicate Release test added 6m38s of macOS runner time without testing different code or a different product graph.

Verification

🤖 Generated with Claude Code

Require successful exact-commit PR CI and CodeQL evidence before signing, then reuse those reviewed results instead of running the same newest-Xcode test suite again in Release. Keep signing, notarization, Gatekeeper, checksums, publication, and Homebrew validation unchanged.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@blessdyb
blessdyb merged commit 3cda4d8 into main Nov 4, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant