updating version to 2.0.3

taimoorq · taimoorq · commit d2c054e35fee · 2026-05-22T18:36:17.000-04:00
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -2,6 +2,16 @@
 
 All notable changes to Logister will be documented in this file.
 
+## v2.0.3 - 2026-05-22
+
+### Added
+
+- Added cached release update checks and a dismissible navigation notification so operators can see when a newer Logister version is available.
+
+### Changed
+
+- Updated public self-hosting references for the `v2.0.3` release image tag.
+
 ## v2.0.2 - 2026-05-22
 
 ### Changed
diff --git a/README.md b/README.md
@@ -117,9 +117,9 @@ This is the shortest production path. Use the public docs when you need provider
 2. Choose an app image.
 
    ```bash
-   docker pull ghcr.io/taimoorq/logister:v2.0.2
+   docker pull ghcr.io/taimoorq/logister:v2.0.3
    # or
-   docker pull docker.io/taimoorq/logister:v2.0.2
+   docker pull docker.io/taimoorq/logister:v2.0.3
    ```
 
 3. Create production config from the sample.
@@ -252,10 +252,10 @@ The repo uses `.env.sample` as the example environment file. For self-hosted pro
 
 Release images are published to GitHub Container Registry and Docker Hub after CI, Fly deploy, and Fly health checks pass. The production `Dockerfile` still lets you build locally, but self-hosters can usually pull the versioned image:
 
-- `ghcr.io/taimoorq/logister:v2.0.2`
+- `ghcr.io/taimoorq/logister:v2.0.3`
 - `ghcr.io/taimoorq/logister:latest`
 - `ghcr.io/taimoorq/logister:<short-sha>`
-- `docker.io/taimoorq/logister:v2.0.2`
+- `docker.io/taimoorq/logister:v2.0.3`
 - `docker.io/taimoorq/logister:latest`
 - `docker.io/taimoorq/logister:<short-sha>`
 
diff --git a/app/views/home/show.html.erb b/app/views/home/show.html.erb
@@ -18,7 +18,7 @@
     "https://github.com/taimoorq/logister/pkgs/container/logister",
     "https://hub.docker.com/r/taimoorq/logister"
   ],
-  "softwareVersion" => "2.0.2",
+  "softwareVersion" => "2.0.3",
   "keywords" => "open source error monitoring, self-hosted bug tracking, Bugsnag alternative, Bugzilla alternative, Sentry alternative, application observability, Rails error tracking, Docker self hosting",
   "sameAs" => [
     "https://github.com/taimoorq/logister",
diff --git a/cloudflare-docs/llms-full.txt b/cloudflare-docs/llms-full.txt
@@ -87,7 +87,7 @@ All maintained add-ons send the same core telemetry families into the main app:
 - GHCR package: https://github.com/taimoorq/logister/pkgs/container/logister
 - Docker Hub package: https://hub.docker.com/r/taimoorq/logister
 - Optional Quay mirror: `quay.io/taimoorq/logister` when `QUAY_USERNAME` and `QUAY_TOKEN` are configured
-- Current versioned images: `ghcr.io/taimoorq/logister:v2.0.2` or `docker.io/taimoorq/logister:v2.0.2`
+- Current versioned images: `ghcr.io/taimoorq/logister:v2.0.3` or `docker.io/taimoorq/logister:v2.0.3`
 - Latest images: `ghcr.io/taimoorq/logister:latest` or `docker.io/taimoorq/logister:latest`
 - Release workflow publishes version, latest, and short-SHA Docker tags to GHCR and Docker Hub after CI, Fly deploy, and health checks pass. It publishes the same tags to Quay when Quay credentials are present.
 
diff --git a/cloudflare-docs/llms.txt b/cloudflare-docs/llms.txt
@@ -47,7 +47,7 @@ The public hosted app at logister.org is a secondary option. The primary goal is
 - GHCR image package: https://github.com/taimoorq/logister/pkgs/container/logister
 - Docker Hub image package: https://hub.docker.com/r/taimoorq/logister
 - Optional Quay image mirror: `quay.io/taimoorq/logister` when Quay credentials are configured in the release workflow
-- Versioned Docker images: `ghcr.io/taimoorq/logister:v2.0.2` or `docker.io/taimoorq/logister:v2.0.2`
+- Versioned Docker images: `ghcr.io/taimoorq/logister:v2.0.3` or `docker.io/taimoorq/logister:v2.0.3`
 - Latest Docker images: `ghcr.io/taimoorq/logister:latest` or `docker.io/taimoorq/logister:latest`
 - Supported baseline infrastructure: Rails, PostgreSQL, Redis, Sidekiq, SMTP/Amazon SES, optional S3-compatible archive storage, and optional ClickHouse
 - Production setup order: provision PostgreSQL and Redis, set required secrets from `.env.sample`, run `./bin/release`, start one web process and one Sidekiq worker, verify `/up`, sign-in, project creation, API key generation, and a test inbox event, then enable optional services.
diff --git a/cloudflare-docs/self-hosting/index.html b/cloudflare-docs/self-hosting/index.html
@@ -181,12 +181,12 @@ <h2>Run the app image with managed services or a Compose-backed single-host stac
                   <span class="code-language">shell</span>
                   <button class="copy-button" data-copy-button data-copy-target="#docker-build-code">Copy</button>
                 </div>
-                <pre><code id="docker-build-code">docker pull ghcr.io/taimoorq/logister:v2.0.2
-docker pull docker.io/taimoorq/logister:v2.0.2
+                <pre><code id="docker-build-code">docker pull ghcr.io/taimoorq/logister:v2.0.3
+docker pull docker.io/taimoorq/logister:v2.0.3
 cp .env.sample .env.production
 # Edit .env.production with production URLs and secrets before starting containers.</code></pre>
               </div>
-              <p>Each release publishes three image tags to the configured registries: the version tag such as <code>v2.0.2</code>, <code>latest</code>, and the short commit SHA. GHCR and Docker Hub are the default public registries; Quay can be enabled as an additional mirror. If you prefer to build from source, the repository still includes a production <code>Dockerfile</code>.</p>
+              <p>Each release publishes three image tags to the configured registries: the version tag such as <code>v2.0.3</code>, <code>latest</code>, and the short commit SHA. GHCR and Docker Hub are the default public registries; Quay can be enabled as an additional mirror. If you prefer to build from source, the repository still includes a production <code>Dockerfile</code>.</p>
               <table>
                 <thead><tr><th>Docker shape</th><th>Use when</th><th>Notes</th></tr></thead>
                 <tbody>
@@ -203,7 +203,7 @@ <h2>Run the app image with managed services or a Compose-backed single-host stac
                 </div>
                 <pre><code id="docker-compose-selfhost-code">services:
   web:
-    image: ghcr.io/taimoorq/logister:v2.0.2
+    image: ghcr.io/taimoorq/logister:v2.0.3
     env_file: .env.production
     command: ./bin/thrust ./bin/rails server -b 0.0.0.0 -p 80
     ports:
@@ -213,7 +213,7 @@ <h2>Run the app image with managed services or a Compose-backed single-host stac
       - redis
 
   worker:
-    image: ghcr.io/taimoorq/logister:v2.0.2
+    image: ghcr.io/taimoorq/logister:v2.0.3
     env_file: .env.production
     command: bundle exec sidekiq -C config/sidekiq.yml
     depends_on:
diff --git a/cloudflare-docs/use-cases/bugsnag-alternative/index.html b/cloudflare-docs/use-cases/bugsnag-alternative/index.html
@@ -33,7 +33,7 @@
           <article class="article">
             <section class="section"><p class="eyebrow">When Logister fits</p><h2>Choose Logister when alerts need to become owned work.</h2><p>Logister groups repeated exceptions into issue-like error groups, then lets teams assign owners, filter inboxes by assignment, mark issues fixed, ignore noise, archive historical work, and inspect request context before deciding what to do.</p></section>
             <section class="section"><p class="eyebrow">Notifications</p><h2>Keep email relevant.</h2><p>Project notification preferences support first-occurrence emails for new error groups plus daily or weekly digest summaries. Self-hosted installs use standard Rails SMTP settings, commonly backed by Amazon SES, and Sidekiq sends mail outside the web request.</p><ul><li>First occurrence alerts highlight new error types.</li><li>Digest emails summarize project error activity without mailing every repeat occurrence.</li><li>Email content includes project, environment, release, occurrence, and triage links when available.</li></ul></section>
-            <section class="section"><p class="eyebrow">Operations</p><h2>Run releases from your own infrastructure path.</h2><p>Versioned Docker images are published to GHCR and Docker Hub after CI, Fly deploy, and health checks pass, with optional Quay mirrors when configured. Self-hosters can pin a version such as <code>ghcr.io/taimoorq/logister:v2.0.2</code> or <code>docker.io/taimoorq/logister:v2.0.2</code>, use <code>latest</code>, or build from source.</p><p><a href="/self-hosting/#docker">Read the Docker self-hosting guide</a>.</p></section>
+            <section class="section"><p class="eyebrow">Operations</p><h2>Run releases from your own infrastructure path.</h2><p>Versioned Docker images are published to GHCR and Docker Hub after CI, Fly deploy, and health checks pass, with optional Quay mirrors when configured. Self-hosters can pin a version such as <code>ghcr.io/taimoorq/logister:v2.0.3</code> or <code>docker.io/taimoorq/logister:v2.0.3</code>, use <code>latest</code>, or build from source.</p><p><a href="/self-hosting/#docker">Read the Docker self-hosting guide</a>.</p></section>
           </article>
         </div>
       </main>
diff --git a/cloudflare-docs/use-cases/docker-ghcr-self-hosting/index.html b/cloudflare-docs/use-cases/docker-ghcr-self-hosting/index.html
@@ -32,7 +32,7 @@
         <div class="docs-layout">
           <aside class="sidebar"><div class="sidebar-group"><p class="sidebar-label">Use cases</p><a href="/use-cases/self-hosted-error-monitoring/">Self-hosted error monitoring</a><a class="active" href="/use-cases/docker-ghcr-self-hosting/">Docker registries</a><a href="/use-cases/error-assignment-team-triage/">Team triage</a><a href="/use-cases/amazon-ses-error-alerts/">SES alerts</a></div><div class="sidebar-group"><p class="sidebar-label">Operations</p><a href="/self-hosting/#docker">Docker guide</a><a href="/deployment/">Environment reference</a><a href="https://github.com/taimoorq/logister/pkgs/container/logister">GHCR package</a><a href="https://hub.docker.com/r/taimoorq/logister">Docker Hub package</a></div></aside>
           <article class="article">
-            <section class="section"><p class="eyebrow">Release images</p><h2>Pin the app image that matches the release notes.</h2><p>Release automation publishes version, latest, and short-SHA tags to GHCR and Docker Hub after CI, Fly deploy, and health checks pass. It can also publish the same tags to Quay when the release workflow has <code>QUAY_USERNAME</code> and <code>QUAY_TOKEN</code>. For stable self-hosting, pin a version tag such as <code>ghcr.io/taimoorq/logister:v2.0.2</code> or <code>docker.io/taimoorq/logister:v2.0.2</code> and review the matching changelog entry before upgrading.</p></section>
+            <section class="section"><p class="eyebrow">Release images</p><h2>Pin the app image that matches the release notes.</h2><p>Release automation publishes version, latest, and short-SHA tags to GHCR and Docker Hub after CI, Fly deploy, and health checks pass. It can also publish the same tags to Quay when the release workflow has <code>QUAY_USERNAME</code> and <code>QUAY_TOKEN</code>. For stable self-hosting, pin a version tag such as <code>ghcr.io/taimoorq/logister:v2.0.3</code> or <code>docker.io/taimoorq/logister:v2.0.3</code> and review the matching changelog entry before upgrading.</p></section>
             <section class="section"><p class="eyebrow">Process model</p><h2>The Docker shape mirrors the Rails app architecture.</h2><table><thead><tr><th>Container</th><th>Responsibility</th></tr></thead><tbody><tr><td>Web</td><td>Runs the Rails UI, auth, project management, dashboards, and ingest endpoints.</td></tr><tr><td>Worker</td><td>Runs Sidekiq for email delivery, first-occurrence alerts, digests, async ingestion, optional ClickHouse writes, and archive/prune tasks.</td></tr><tr><td>PostgreSQL</td><td>Stores accounts, projects, API keys, events, grouped errors, notification preferences, and sharing.</td></tr><tr><td>Redis</td><td>Backs Sidekiq, caching, and rate-friendly dashboard behavior.</td></tr><tr><td>S3-compatible storage</td><td>Optional Active Storage target for compressed telemetry archives.</td></tr><tr><td>ClickHouse</td><td>Optional analytics store for higher-volume event and span exploration.</td></tr></tbody></table></section>
             <section class="section"><p class="eyebrow">Self-hosting choices</p><h2>Use managed data stores or a single-host stack.</h2><p>Teams can run only the Logister web and worker containers while using managed PostgreSQL, Redis, and SMTP, or they can use a Compose-style single-host stack for the full footprint. The same environment reference applies in both cases.</p><ul><li>Keep secrets in the deploy platform or host secret store, not in the repository.</li><li>Run database migrations in a release phase or explicit one-off task.</li><li>Keep at least one worker process running so email, digests, and async ingestion continue.</li></ul></section>
             <section class="section"><p class="eyebrow">Next steps</p><h2>Start with the Docker guide and environment reference.</h2><div class="card-grid"><article class="card"><h3>Docker self-hosting</h3><p><a href="/self-hosting/#docker">Read the Docker guide</a></p></article><article class="card"><h3>Environment variables</h3><p><a href="/deployment/">Read the env reference</a></p></article><article class="card"><h3>Release images</h3><p><a href="https://github.com/taimoorq/logister/pkgs/container/logister">Open the GHCR package</a> or <a href="https://hub.docker.com/r/taimoorq/logister">Docker Hub package</a></p></article></div></section>
diff --git a/cloudflare-docs/use-cases/self-hosted-error-monitoring/index.html b/cloudflare-docs/use-cases/self-hosted-error-monitoring/index.html
@@ -33,7 +33,7 @@
           <aside class="sidebar"><div class="sidebar-group"><p class="sidebar-label">Use cases</p><a class="active" href="/use-cases/self-hosted-error-monitoring/">Self-hosted error monitoring</a><a href="/use-cases/sentry-alternative/">Sentry alternative</a><a href="/use-cases/bugsnag-alternative/">Bugsnag alternative</a><a href="/use-cases/bugzilla-alternative/">Bugzilla alternative</a></div><div class="sidebar-group"><p class="sidebar-label">Next</p><a href="/self-hosting/">Self-hosting guide</a><a href="/deployment/">Deployment config</a><a href="/getting-started/">Getting started</a></div></aside>
           <article class="article">
             <section class="section"><p class="eyebrow">Best fit</p><h2>Choose this path when data ownership and operational control matter.</h2><p>Logister is built for teams that want application errors, logs, metrics, transactions, spans, check-ins, ownership, and notification preferences in a self-hosted app. The app runs as a Rails web process plus a Sidekiq worker, backed by PostgreSQL and Redis. S3-compatible archive storage can be added when you need export-before-prune retention, and ClickHouse can be added later for higher-volume analytics.</p></section>
-            <section class="section"><p class="eyebrow">Infrastructure</p><h2>The supported self-hosting stack is explicit.</h2><table><thead><tr><th>Part</th><th>Role</th></tr></thead><tbody><tr><td>Rails web process</td><td>Serves the UI, auth, project pages, public pages, and ingest endpoints.</td></tr><tr><td>PostgreSQL</td><td>Stores accounts, projects, API keys, events, error groups, monitors, notification preferences, and project sharing.</td></tr><tr><td>Redis and Sidekiq</td><td>Run background jobs, caching, email delivery, first-occurrence alerts, digest scheduling, optional ClickHouse writes, and archive/prune tasks.</td></tr><tr><td>SMTP / Amazon SES</td><td>Sends auth mail, project first-occurrence alerts, and daily or weekly digests.</td></tr><tr><td>S3-compatible object storage</td><td>Optionally stores compressed JSONL telemetry archive exports before old non-error hot telemetry is pruned from PostgreSQL.</td></tr><tr><td>ClickHouse</td><td>Optionally stores raw event/span analytics copies and one-minute rollups after schema readiness checks pass.</td></tr><tr><td>Registry images</td><td>Provide versioned release images such as <code>ghcr.io/taimoorq/logister:v2.0.2</code> or <code>docker.io/taimoorq/logister:v2.0.2</code>, with optional Quay mirrors when configured.</td></tr></tbody></table></section>
+            <section class="section"><p class="eyebrow">Infrastructure</p><h2>The supported self-hosting stack is explicit.</h2><table><thead><tr><th>Part</th><th>Role</th></tr></thead><tbody><tr><td>Rails web process</td><td>Serves the UI, auth, project pages, public pages, and ingest endpoints.</td></tr><tr><td>PostgreSQL</td><td>Stores accounts, projects, API keys, events, error groups, monitors, notification preferences, and project sharing.</td></tr><tr><td>Redis and Sidekiq</td><td>Run background jobs, caching, email delivery, first-occurrence alerts, digest scheduling, optional ClickHouse writes, and archive/prune tasks.</td></tr><tr><td>SMTP / Amazon SES</td><td>Sends auth mail, project first-occurrence alerts, and daily or weekly digests.</td></tr><tr><td>S3-compatible object storage</td><td>Optionally stores compressed JSONL telemetry archive exports before old non-error hot telemetry is pruned from PostgreSQL.</td></tr><tr><td>ClickHouse</td><td>Optionally stores raw event/span analytics copies and one-minute rollups after schema readiness checks pass.</td></tr><tr><td>Registry images</td><td>Provide versioned release images such as <code>ghcr.io/taimoorq/logister:v2.0.3</code> or <code>docker.io/taimoorq/logister:v2.0.3</code>, with optional Quay mirrors when configured.</td></tr></tbody></table></section>
             <section class="section"><p class="eyebrow">Why it helps</p><h2>Self-hosting does not have to mean inventing the product surface yourself.</h2><ul><li>Grouped errors become assignable work with status, occurrence history, and request context.</li><li>Dashboard explorer charts use server-backed aggregate endpoints instead of loading every event into the browser.</li><li>Archived projects stay accessible but disappear from active dashboards and revoke active API keys.</li><li>Release notes, Docker images, docs, and environment variable references are published together for repeatable operations.</li></ul></section>
             <section class="section"><p class="eyebrow">Next steps</p><h2>Start with the deployment docs, then connect one service.</h2><div class="card-grid"><article class="card"><h3>Plan infrastructure</h3><p><a href="/self-hosting/">Read self-hosting docs</a></p></article><article class="card"><h3>Set environment variables</h3><p><a href="/deployment/">Read deployment config</a></p></article><article class="card"><h3>Send the first event</h3><p><a href="/getting-started/">Read getting started</a></p></article></div></section>
           </article>
diff --git a/docs/seo-llm-measurement-runbook.md b/docs/seo-llm-measurement-runbook.md
@@ -126,13 +126,13 @@ Suggested checks:
 
 ```bash
 gh repo view taimoorq/logister --json description,homepageUrl,repositoryTopics,url
-gh release view v2.0.2 --json tagName,isLatest,isDraft,isPrerelease,publishedAt,url
+gh release view v2.0.3 --json tagName,isLatest,isDraft,isPrerelease,publishedAt,url
 gh api /user/packages/container/logister --jq '{name, visibility, html_url}'
 gh api /user/packages/container/logister/versions --jq '.[] | {id, tags: .metadata.container.tags, updated_at}'
-docker pull ghcr.io/taimoorq/logister:v2.0.2
-docker pull docker.io/taimoorq/logister:v2.0.2
+docker pull ghcr.io/taimoorq/logister:v2.0.3
+docker pull docker.io/taimoorq/logister:v2.0.3
 # Optional, when the Quay.io mirror is configured:
-docker pull quay.io/taimoorq/logister:v2.0.2
+docker pull quay.io/taimoorq/logister:v2.0.3
 ```
 
 ## Package and SDK Checks
diff --git a/public/llms-full.txt b/public/llms-full.txt
@@ -61,7 +61,7 @@ All maintained add-ons send the same core telemetry families into the main app:
 - GHCR package: https://github.com/taimoorq/logister/pkgs/container/logister
 - Docker Hub package: https://hub.docker.com/r/taimoorq/logister
 - Optional Quay mirror: `quay.io/taimoorq/logister` when `QUAY_USERNAME` and `QUAY_TOKEN` are configured
-- Current versioned images: `ghcr.io/taimoorq/logister:v2.0.2` or `docker.io/taimoorq/logister:v2.0.2`
+- Current versioned images: `ghcr.io/taimoorq/logister:v2.0.3` or `docker.io/taimoorq/logister:v2.0.3`
 - Latest images: `ghcr.io/taimoorq/logister:latest` or `docker.io/taimoorq/logister:latest`
 - Release workflow publishes version, latest, and short-SHA Docker tags to GHCR and Docker Hub after CI, Fly deploy, and health checks pass. It publishes the same tags to Quay when Quay credentials are present.
 
diff --git a/public/llms.txt b/public/llms.txt
diff --git a/spec/requests/dashboard_spec.rb b/spec/requests/dashboard_spec.rb
diff --git a/spec/requests/home_spec.rb b/spec/requests/home_spec.rb
diff --git a/spec/requests/routes_protection_spec.rb b/spec/requests/routes_protection_spec.rb
diff --git a/spec/services/logister/release_update_checker_spec.rb b/spec/services/logister/release_update_checker_spec.rb
