0.3.340
0.3.340
Bug Fixes
-
portal 1.8.56 → 1.8.57 — fixes a live regression introduced in 1.8.56 (shipped as 0.3.339) where every composition detail page resolved nothing for admin-level callers. Before the fix: 1 of 44 compositions resolved; after: 44 of 44.
Root cause: portal-1.8.56 changed composition-detail, -editdef, -events, and -resources to fan out
foundas per-namespace LISTs over 46 kinds. snowplow's cluster-list collapse replaces a multi-namespace iterator with a single cluster list keyed on the first element's kind only, so every other kind went unread. The fix iterates unique kinds and issues one cluster-scope list per kind, plus auserAccessFilterso namespace-scoped tenants still see only their own compositions.Known cost: the
userAccessFilteron these four high-traffic RestActions causes snowplow to decline their L1 cache puts (cache key does not fold UAF scope until snowplow v7/1.13.0). The composition-detail pages are now uncached until that snowplow release lands. Correctness was chosen over cache.portal-agents moves from 1.8.56 → 1.8.57 in lockstep (Chart.yaml only; no functional change).
Files changed: chart/files/component-pins.yaml (portal and portal-agents pin update).