Skip to content

Remembra v5.0.1 — Security and Migration Hotfix

Choose a tag to compare

View all tags
@lacrous lacrous released this 24 Sep 15:22
· 156 commits to main since this release
v5.0.1
ba3be3e

Remembra 5.0.1

V5.0.1 is the security, storage, history, and tenant-snapshot correctness hotfix for the V5 platform. It preserves V4.9/V5 compatibility and does not introduce V6 behavior.

Security and reliability fixes

  • Authenticates requests before consuming protected rate-limit buckets; anonymous and authenticated identities are isolated and opaque.
  • Adds centralized secret redaction for structured logs, debug search diagnostics, provider errors, nested headers, and credentials; public provider errors are sanitized.
  • Makes SQLite initialization and startup migration readiness fail closed. The file backend is available only with REMEMBRA_ALLOW_FILE_FALLBACK=1, is warned about, and is reported by health.
  • Validates and contains file-history paths and rejects symlinked history storage/sidecars.
  • Rejects tenantless snapshots during ordinary strict restore before any write.

Explicit tenant migration

  • Adds read-only remembra migrate analyze.
  • Adds signed, target-bound remembra migrate plan and migrate apply --dry-run/apply commands.
  • Requires a trusted strict operator tenant and signed snapshot key; ordinary import cannot enable migration.
  • Verifies plan signatures, snapshot digests, manifests, and destination tenant scope; repeated applies are idempotent.

Verification

  • Node 18.20.8: complete release gate passed.
  • Node 24.21.0: complete release gate passed.
  • Full suite: 414 passed, 0 failed; security matrix: 47 passed; recovery matrix: 13 passed.
  • Documentation check: 35 files passed; dependency audit: 0 vulnerabilities.
  • Package dry-run: 203 files, approximately 410 kB compressed.

Upgrade and rollback guidance

Read the V5.0.1 security and migration guide before enabling strict tenant restore or explicit migration. Keep a verified backup before applying a tenant plan; a failed migration must be investigated and restored/retried with the same signed, target-bound plan.

Artifacts

Assets 2
Loading