keel: move to 0.4.0, and pin the api at one replica #30

Merged

PerishFire merged 1 commit from keel-040 into main

2026-07-21 08:14:15 +00:00

PerishFire commented

2026-07-21 08:11:39 +00:00

Owner

No description provided.

PerishFire added 1 commit

2026-07-21 08:11:39 +00:00

keel: move to 0.4.0, and pin the api at one replica

guard / guard (pull_request) Successful in 2m27s

Details

b55599128a

Dependency line only. 0.4.0 renames set_tie to tune and reshuffles
query's internals, none of which codehull calls — checked across the tree
rather than assumed, as with 0.3.0's Vault::open.

What does reach codehull is the cache fix. codehull already exposes the
switch: keel.toml [cache] kind = "none" becomes Hold::None becomes
core.bare(). Before keel #105 that call left grant rows cached, so anyone
setting cache = none to prepare a multi-replica deploy still had
authority held per process. It now clears both caches.

The chart says why replicas stays at 1, at the line someone would change:
keel caches grants per engine instance, so a second api pod keeps
honouring a grant this one revoked until it writes. Raising it needs the
cache off first. helm lint clean.

Verified with the blob path actually running — KEEL_S3 set, act 5's
presigned upload and gated download green — since guard skips it
otherwise and that is the acceptance this repo cares about.

PerishFire merged commit e0283b73ec into main

2026-07-21 08:14:15 +00:00

PerishFire deleted branch keel-040

2026-07-21 08:14:15 +00:00

PerishFire referenced this pull request from a commit

2026-07-21 08:14:16 +00:00

keel: move to 0.4.0, and pin the api at one replica (#30)