v0.1.2

Changes since v0.1.1

• fix(auth): improve whoami error recovery (9e5bd7f)
• fix(auth): sign out on whoami permission denial (80da531)
• fix(auth): isolate whoami session expiry behavior (67c19d5)
• feat:add entitlement screen for no roles users (2b81b4a)
• fix: move to OpenShell 0.1.5 (f861a46)
• fix(backend): pass sandbox creates the SDK's create options (4f6fda8)
• feat(sandbox): show why a tool server exchange or a token grant failed (a83a4cc)
• Add live logs streaming (#124) (0eda172)
• feat(pagination): add server-side pagination and label filters (RHOAIENG-98858) (#122) (61e2590)
• feat(ui): a cohesive redesign around the admin's core flows (#123) (70afb39)
• test(e2e): scroll a sandbox row into view before checking it (#127) (3b9560a)

Everything between v0.1.1 and v0.1.2

Supported OpenShell gateways

0.1.x, tested on 0.1.5, built against OpenShell Go SDK v0.0.0-20261020123705-bdb956f2cd65.

This release is for the gateway 0.1.x release line: any patch release of it, and any pre-release or rebuild of one. The release named above is the one this commit is built on and passed the compatibility suite against. A gateway on another release line is not supported by this release; see Compatibility for which dashboard to run instead.

Upgrading the gateway from 0.1.4 to 0.1.5

Sandboxes created on gateway 0.1.4 may not start after the gateway moves to 0.1.5. Seen with the Docker compute driver: the sandbox goes to ERROR with Failed to start sandbox during gateway startup: decode Docker sandbox bootstrap for authentication rotation: unknown field 'outer_fence'. This is the gateway's upgrade, not the dashboard: the Gateway page lists such a sandbox under Needs attention as a sandbox error. Recreate the sandbox after the upgrade. The Kubernetes driver was not tested.