KumaEdge v0.20.2 — Open-Source Product Launch

KumaEdge v0.20.2 is deployed at https://mc-b4n2u1709h.bunny.run/demo — public demo / demo, read-only.

Product launch

• English product README with original Obsidian Cloud SVG branding, real desktop/mobile/login/isolated OWNER/themed Status Page screenshots, Mermaid architecture and clear quick start.
• Current installation/configuration/CSS/security/backup/restore/upgrade/rollback/troubleshooting docs; canonical Bunny affiliate URL with disclosure.
• GitHub description, homepage and all ten topics updated. Social preview PNG (1280×640, <1MB) prepared with exact manual upload instructions; not claimed installed.
• Explicit public-demo opt-in stores a salted scrypt verifier. Private password policy, OWNER/admin/TOTP and read-only allowlist boundaries remain intact. Public login resource controls account for a shared CDN peer.
• New-install state protection and correct public protected-gateway checks. No GitHub Actions.

Verified results

100 Node + 52 Python tests without skips; full local Docker/OCI tests and immutable publication/pullback PASS. Real public demo/demo and wrong-password browser tests, mobile no-overflow, no application console errors, HTTPS/private cache/WebSocket/CSRF/session/tamper/logout/OWNER isolation/affiliate acceptance PASS. Fresh actual Bunny full-volume encrypted backup and isolated local restore PASS. Original owner authentication, monitor/Status Page configuration and volume instance preserved. Final Terraform plan no-op; no additional paid resources.

PR #45 and #46 are merged. README assets, links and Mermaid verified in main in a real browser.

Exact provenance

• Runtime source: 255f88d5d3721ad15d838c2fa54c9f00efcb12e2.
• Main/tag merge commit: 294c9f84dded9cda6352102f2be22b1cb0c2546c; its tree is identical to the tested runtime source tree. A merge SHA is not another published image tag.
• Main OCI: ghcr.io/aitishnyk/kumaedge:255f88d5d3721ad15d838c2fa54c9f00efcb12e2@sha256:24dafd62492e476d203f413939159fb7f7b00e5a5081fa6a33d770f5d80d83d9.
• Paired backup OCI: ghcr.io/aitishnyk/kumaedge-backup:255f88d5d3721ad15d838c2fa54c9f00efcb12e2@sha256:a6e89d99547cb936e56d9693bbeb18a6ad8cdfafc073671e918652d87e839ccb.
• Original engine: Uptime Kuma 2.5.7, unchanged.

Use the attached evidence.json and its runtime SHA/digests for digest-pinned installation, rather than inventing an image tag from the merge commit. The source/runtime mapping and acceptance summary are attached. Previous immutable images, encrypted backups and private state remain available for operator-reviewed rollback.

Limits

Readiness is DEMO_READY, not PRODUCTION_READY. External notification delivery is NOT_VERIFIED (no channel). Interactive current admin TOTP login is NOT_RETESTED; authentication preservation is verified by encrypted before/after snapshots. Full-duration public session expiry was not waited out (local regression PASS). Bunny-to-Bunny restore is NOT_RUN because extra cloud resources are forbidden. Social-preview upload remains a manual owner step documented in docs/BRANDING.md.

KumaEdge v0.20.0 — Integrated Demo Mode & Bunny Live Hardening

KumaEdge v0.20.0 preserves original Uptime Kuma 2.5.7 and adds an independent, server-enforced read-only DEMO inside the existing owner gateway.

Accepted readiness: DEMO_READY. OWNER Basic + original Kuma admin/TOTP, DEMO login/public metrics/isolation/CSRF/logout/restart invalidation, real HTTPS/polling/WebSocket/reconnect, private no-store CDN, real monitoring/controlled DOWN-UP, independent heartbeat collection, same-volume restart, full actual Bunny-source encrypted backup and independent isolated local restore passed.

External notification delivery remains NOT_VERIFIED: the owner confirmed no channel exists. Bunny-to-Bunny restore is NOT_RUN, since additional paid resources are forbidden. Mobile-browser layout and full public one-hour session-expiry duration are NOT_RUN; local server TTL regression passes. This release does not claim PRODUCTION_READY.

Immutable runtime source: 5c2bd701758944b609dfd588ed12b3f97624c51b.

• Main: ghcr.io/aitishnyk/kumaedge:5c2bd701758944b609dfd588ed12b3f97624c51b@sha256:55b4f8a88396fa6b75163ee41c94c2cf0926e60a46cff8986913eb4ea3c99c48
• Paired backup artifact: ghcr.io/aitishnyk/kumaedge-backup:5c2bd701758944b609dfd588ed12b3f97624c51b@sha256:0b2c35cba40672523730217e39a701257ec9ef14ae7fdb561b0f4a044c881d22

The release tag also includes final live documentation and an operator-only longer bounded restart wait/private cookie retention. Those follow-ups do not change Docker runtime inputs. Do not assume a later main/docs SHA is a published image SHA.

Validation ran locally on the owner's Mac: 89 Node + 51 Python tests without skips, both Linux/AMD64 images, real engine/TOTP/TLS/STARTTLS/monitoring/DR/migration, immutable GHCR digest verification and pull-back identity. GitHub Actions were not used and repository Actions remain disabled.

Existing Bunny app, two containers, one DE replica, original 5GB volume/instance, CDN zone and HTTPS endpoint are preserved. New paid resources: 0. Final Terraform plan: NO_CHANGES. The old disposable data reset was explicitly owner-authorized and performed only once; the final image update did not reset data or rotate credentials.

See live acceptance, release/rollback, and attached sanitized evidence. State, secrets, plaintext backups and recovery identities remain private.

KumaEdge v0.19.0-rc.1 — Local Verified Candidate

KumaEdge v0.19.0-rc.1 is a locally verified release candidate using official Uptime Kuma 2.5.7. DEPLOYMENT_BLOCKED: the paid Bunny plan awaits the owner's explicit confirmation in their trusted local terminal. No public demo or production certification is claimed.

Source: 21febcb9e2bdd4bb88f3d374b9dc59d451e80d01; merged by PR #43 as 0118c99819e5f700e041d7f2995fe62cb5bc30de. Both commits have the same Git tree. Images are pinned to the tested source SHA, not falsely attributed to the merge commit.

• Main: ghcr.io/aitishnyk/kumaedge:21febcb9e2bdd4bb88f3d374b9dc59d451e80d01 — sha256:23ba069c5e5b2233a9c5df2aa62b7c9d681f4e135cc08024987b5652b0bec9e7
• Backup: ghcr.io/aitishnyk/kumaedge-backup:21febcb9e2bdd4bb88f3d374b9dc59d451e80d01 — sha256:c5d6f913c9dcb6b63840ae3ecb19981bc9716a3fddc6d31e305bb184efe469bd

Both Linux/AMD64 images were built locally on Docker Desktop, pushed from the Mac, pulled back, and checked against tested Docker image identities and re-read registry manifests. Initial GHCR upload timeouts were resolved with guarded retries. No SHA tag was overwritten.

Validation: Node 82 PASS; Python 36 PASS without skips; both Terraform modules init/fmt/validate PASS; real Kuma monitoring, authenticated/anonymous polling and WebSocket, owner gateway, TOTP, local DOWN/UP webhook receipts, persistence across restart, 2.5.6→2.5.7 migration, trusted TLS/STARTTLS, encrypted complete-volume recovery and pre-upgrade backup rollback to the old engine PASS. Source and image metadata credential-pattern scans passed. Local evidence is unsigned operator evidence, not GitHub Actions provenance.

Bunny plan: one app, one replica, DE, 5 GB persistent /app/data, private original Kuma plus protected CDN gateway; two resource creates and no deletions. Apply NOT_RUN. Public TLS/cache/session, live notifications, Bunny restart/persistence and full Bunny-volume restore remain NOT_RUN.

Upstream #8019 remains open: untrusted self-signed TCP SSL certificates are rejected. Audit trust configuration and supply a narrowly trusted CA; global TLS verification was not disabled. Never roll back by opening a migrated database with an older engine: restore the pre-upgrade full volume into a separate volume first.

GitHub Actions release workflows are archived/disabled. The separately configured default CodeQL setup was also disabled after GitHub automatically created two failed PR runs; those runs were not release evidence. The hosted-runner fault is not claimed fixed. v1.0 remains gated on complete live certification.