Skip to content

chore(console): ship admin dashboard v0.9.1 #369

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Bccorb merged 1 commit into from
Oct 7, 2026
Merged

chore(console): ship admin dashboard v0.9.1 #369

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/console-dashboard-v0-9-1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'seamless-auth-api': patch
---

Ship admin dashboard `v0.9.1` at `/console` (was `v0.7.0`). It adds the passkey enrollment view, the authentication coverage report, the audit trail panel, the phishing-resistant-only setting, ranged headline metrics and anomalies, and the store review accounts notice, which use routes this API now serves.
9 changes: 4 additions & 5 deletions Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,16 +19,15 @@ RUN npm prune --omit=dev
# (`build:console` sets VITE_BASE_PATH=/console/ and VITE_SAME_ORIGIN=true, so assets, the
# React Router basename, and the origin-derived API base all agree). This API then serves the
# result at /console. The dashboard repo is public, but its npm package is not published
# (package.json is marked private), so it is fetched from git. The pinned ref is a commit that
# includes the dashboard's same-origin build; bump SEAMLESS_ADMIN_DASHBOARD_REF (to a release
# tag once one is cut) to ship a new dashboard on the next auth-image release. Never point a
# release build at a floating branch.
# (package.json is marked private), so it is fetched from git. Bump
# SEAMLESS_ADMIN_DASHBOARD_REF to a dashboard release tag to ship a new dashboard on the next
# auth-image release. Never point a release build at a floating branch.
FROM node:24-slim AS admin-dashboard
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.7.0
ARG SEAMLESS_ADMIN_DASHBOARD_REF=v0.9.1

RUN apt-get update && \
apt-get install -y git python3 make g++ && \
Expand Down
2 changes: 1 addition & 1 deletion docs/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -230,7 +230,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.7.0`;
upstream auth-image release. The ref is pinned to the dashboard release tag `v0.9.1`;
`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
Expand Down
Loading