Overview
Today About Glean in the Admin → Settings area shows the current UI and server versions (including branch name, encoded date such as fe-release-2026-02-26-…, and commit hash). That makes it possible to infer roughly when the tenant was updated, but it’s still not clear:
- What that release means to admins and end users (features, fixes, breaking changes)
- How the current release compares to prior releases applied to this tenant
- How to quickly map observed behavior back to a specific release and its notes
This idea is to add a tenant-scoped release history view with linked release notes, not just raw version identifiers.
Proposed behavior
Add a “Release history” section under Admin → Settings → About Glean that shows:
- Current release
- Version(s) (UI, server, other major components)
- Applied date/time in the tenant’s primary timezone
- Link to release notes (summary) and, if available, detailed changelog
- Historical releases list (e.g., table or timeline):
- Release date/time applied to this tenant
- Version(s) (UI, server, etc.)
- Release type (e.g., minor, major, hotfix, maintenance)
- Link to release notes
- Optional: tags/labels (e.g., “search quality,” “Slack connector,” “admin UX”) to help admins scan for relevant changes
