From 5af06cd8262d543bc7a1eb2c99db62cbc4d7c269 Mon Sep 17 00:00:00 2001 From: Brandon Corbett Date: Tue, 8 Sep 2026 15:38:02 -0400 Subject: [PATCH] chore: ship admin dashboard v0.6.0 in the API image Move SEAMLESS_ADMIN_DASHBOARD_REF from v0.5.0 to v0.6.0 so the SPA served at /console picks up that release. Organizations pages and searches on the server and gains a remove action, Overview and Security take a date range, and System Configuration grows an Authenticator Policy section covering all seven fields. Each of those needs API support that is already in place here: DELETE /admin/organizations/:organizationId exists, the organization list accepts limit, offset and search, the internal metrics endpoints take from and to, and authenticator_policy is a system config key. The ref stays a release tag rather than a floating branch, so the dashboard only changes when this value does. --- .changeset/olive-moons-shave.md | 18 ++++++++++++++++++ Dockerfile | 2 +- docs/configuration.md | 2 +- 3 files changed, 20 insertions(+), 2 deletions(-) create mode 100644 .changeset/olive-moons-shave.md diff --git a/.changeset/olive-moons-shave.md b/.changeset/olive-moons-shave.md new file mode 100644 index 0000000..e779839 --- /dev/null +++ b/.changeset/olive-moons-shave.md @@ -0,0 +1,18 @@ +--- +'seamless-auth-api': minor +--- + +Ship admin dashboard v0.6.0 in the API image. + +`SEAMLESS_ADMIN_DASHBOARD_REF` moves from v0.5.0 to v0.6.0, so the SPA served at `/console` picks +up that release. Organizations pages and searches on the server and gains a remove action, +Overview and Security take a date range, and System Configuration grows an Authenticator Policy +section covering all seven fields. + +Each of those needs API support that is already in place here: `DELETE +/admin/organizations/:organizationId` exists, the organization list accepts `limit`, `offset` and +`search`, the internal metrics endpoints take `from` and `to`, and `authenticator_policy` is a +system config key. + +The ref is a release tag rather than a floating branch, so the dashboard only changes when this +value does. diff --git a/Dockerfile b/Dockerfile index 642c99e..5223cdb 100644 --- a/Dockerfile +++ b/Dockerfile @@ -28,7 +28,7 @@ WORKDIR /dashboard ARG SEAMLESS_ADMIN_DASHBOARD_REPO=https://github.com/fells-code/seamless-auth-admin-dashboard.git # Pinned dashboard release tag. The same-origin /console build has shipped since v0.2.0. -ARG SEAMLESS_ADMIN_DASHBOARD_REF=v0.5.0 +ARG SEAMLESS_ADMIN_DASHBOARD_REF=v0.6.0 RUN apt-get update && \ apt-get install -y git python3 make g++ && \ diff --git a/docs/configuration.md b/docs/configuration.md index 3697c18..cde3dee 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -195,7 +195,7 @@ sets `VITE_BASE_PATH=/console/` and `VITE_SAME_ORIGIN=true` so the assets, the r and the origin-derived API base all agree) in a dedicated stage (see the `admin-dashboard` stage in [`Dockerfile`](../Dockerfile)). Bump the dashboard shipped to tenants by raising the `SEAMLESS_ADMIN_DASHBOARD_REF` build ARG; the new version then flows to tenants through the normal -upstream auth-image release. The ref is pinned to the dashboard release tag `v0.5.0`; +upstream auth-image release. The ref is pinned to the dashboard release tag `v0.6.0`; `v0.2.0` was the first release to ship the same-origin `/console` build. Because the same-origin build derives its API base from the page origin **and still speaks the