chore(kache): pin kache 0.15.1 - #207
Open
jmagar wants to merge 1 commit into
Open
Conversation
Bump the CI kache pin to 0.15.1. Verified against the 0.15.1 binary before bumping: - 0.15.0 stops auto-started daemons inheriting KACHE_S3_*; the remote is written into [cache.remote] in config.toml, so this is unaffected. - 0.15.0 versioned the report JSON schema; kache-gate.sh already reads .summary.*, and its real jq pipeline runs clean against 0.15.1 output. - 0.15.1 accepts local_store / daemon_idle_timeout_secs / prefetch_max_bytes / local_max_size with no unknown-key warnings. Note: the cache-key schema reaches v27, so pre-0.14 entries cold-miss.
Closed
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.
Bumps the CI kache pin to 0.15.1.
Verified against the 0.15.1 binary before bumping
KACHE_S3_*[cache.remote]inconfig.toml, which is what the upgrade note prescribeskache-gate.shalready reads.summary.*; ran its real jq pipeline against 0.15.1 outputlocal_store,daemon_idle_timeout_secs,prefetch_max_bytes,local_max_sizeall accepted, no unknown-key warningsNotes
kache.service, so the action owns the daemon and client/daemon versions always match — no version-split risk.