Skip to content

ci: cache verified release baselines and report shared pin drift - #35

Merged
showxu merged 1 commit into
masterfrom
ci/cache-release-baselines
Oct 15, 2026
Merged

showxu merged 1 commit into
masterfrom
ci/cache-release-baselines

Conversation

@showxu

@showxu showxu commented Oct 15, 2026 •

Copy link
Copy Markdown
Member

Reuse complete recollected release baselines for PR and branch API reports. Exact cache keys bind the release commit, verified attached evidence digest, collector version and archive digest, runner image, and Xcode/Swift identity. Restored records verify all recorded inputs and content before use; cache misses recollect the immutable release source. Release validation and publication bypass the cache, and candidate collection always runs fresh.

The settings checker lists callers that differ from latest shared master without changing its enforcement exit status. Documentation, generated workflows and tests describe the same behavior.

Validation: Scripts/check passed all 59 tests, workflow generation checks and actionlint. An actual pinned swift-semver consumer passed its full hosted validation.

On the same hosted runner-image/toolchain cache key, baseline recollection took 495.140 seconds on a miss and verified reuse took 3.803 seconds on a hit. The complete API jobs took 1,138 and 738 seconds respectively (35.1% shorter); fresh candidate collection remained enabled. The miss run's production steps completed successfully; a temporary study assertion incorrectly assumed a second attempt would hit across a hosted-image change. The final diagnostic verifies the matching cache inputs and complete baseline/candidate evidence. Different image versions produced distinct keys, as required.

@showxu
showxu merged commit 43cc21f into master Oct 15, 2026
4 checks passed
@showxu
showxu deleted the ci/cache-release-baselines branch October 15, 2026 07:09
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