fix(ci): isolate kache canary schemas and trusted credentials - #51
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Kache 0.28.1 rejects schema-27 entries retained under the old shared canary prefix. Each trusted probe now uses a version-and-run-specific prefix, preserving both fresh-runner transfer and zero-miss assertions without deleting remote cache entries.
Shared cache credentials are confined to non-PR main events. PRs retain an explicit credentialless compile check. The official action is pinned to its current immutable v1 commit, and contract tests enforce the PR credential boundary and shared prefix.
Validation: workflow-library validator, Actionlint, focused canary security/schema contract, official-action pin test and diff checks pass. The prior probe reached MinIO on retry and identified the incompatible schema; the new trusted probe will verify real reuse after integration.