SendRepute Campaigns v0.1.37

SendRepute Campaigns v0.1.37

• Correct Arabic saved-template previews in Saved Library and campaign template selection, preserving authored email layout and canonical design content.
• Improve dark-mode card, field and section separation without recoloring the authored email.
• Add a consistent animated operation surface for save and send progress, success and errors across templates, lists and campaigns. Queued feedback means accepted into the sending queue, not delivered to recipients. RTL, mobile layouts, reduced motion and accessible status announcements are supported.
• Keep Use in Campaigns pending until the Campaigns save succeeds. A failed save keeps the document available; duplicate returns do not submit another save.
• Correct paid-design history that could label an already acknowledged saved source as needing verification after reload. Suppress the empty recovery-warning flash during initial loading. Actual missing-source and verification failures remain visible. These notices concern saved-design recovery, not a credit refund; financial guards and settlement behavior are unchanged.

Compatibility and safe upgrade

No database migrations are added or changed compared with v0.1.36. This archive is an isolated audited self-hosted build with its real installation wizard, not the website demo. Repository downloads are the supported publication channel; compatible update checkers return immutable same-commit download and checksum URLs. Older attachment-only checkers require the ordinary one-time Git or archive upgrade. Nothing is installed automatically, and publication does not remotely update a customer server.

Before upgrading, back up the complete PostgreSQL database, application data/encryption key and private .env. From the existing project directory inspect local edits with git status --short, then run:

git pull --ff-only && ./setup.sh --mode resume

Resume preserves the existing access mode, including HTTPS. Preserve the Compose project, volumes and encryption key; do not clone over an installation, run two versions against one database, or use docker compose down -v. Archive installations follow the installation guide. See Docker backup instructions and isolated restore instructions. Rollback can require restoring matching database and application-data backups.

Downloads and verification

Versioned repository downloads: ZIP · tar.gz · SHA-256 checksums. Verify checksums before extraction; GitHub Code → Download ZIP is a different snapshot.

The exact archives passed isolated component builds, frontend boundary auditing, portable-lockfile and archive/hash checks, clean production npm installation, disposable real PostgreSQL migration and restart-persistence checks, extracted installation-wizard Chromium checks, activation-gated setup, root and installed-installer GET/HEAD redirects, public route checks and offline paid-settlement upgrade/backup fixtures. Focused offline browser evidence covers real two-window hosted handoff with held persistence, rejection and duplicate/origin/source/state controls, plus Arabic/dark/mobile and reduced-motion feedback. Release allowlist and setup tests and nine saved-history regressions also passed. No customer database, paid generation, real email send or customer-server upgrade was performed.