v0.3.1

What's Changed

• sb-agent-core 0.4.1: keep the last 7 log files by @sb-mcampoe in #4
• v0.3.1: report the signature check before each order (S4) by @sb-mcampoe in #5

Full Changelog: v0.3.0...v0.3.1

v0.3.0

What's Changed

• README fiel al código by @sb-mcampoe in #1
• El instalador descarga la librería común de master by @sb-mcampoe in #2
• restore_snapshot: restaurar copias desde el panel (0.3.0) by @sb-mcampoe in #3

New Contributors

• @sb-mcampoe made their first contribution in #1

Full Changelog: v0.2.3...v0.3.0

v0.2.3

Full Changelog: v0.2.2...v0.2.3

v0.2.2

Full Changelog: v0.2.1...v0.2.2

v0.2.1

Full Changelog: v0.2.0...v0.2.1

v0.2.0

TitanVault v0.2.0 prepares the parallel migration of infra backups while preserving legacy backups.

• Five configurable schedule levels; per-level heartbeats with legacy fallback.
• Recursive snapshot catalog and retention per source and level.
• CLI snapshots, prune --level, and restore to a new destination. Recovery supports encrypted filesystem archives and SQL export; it never imports SQL into the source database.
• Backup/config/encryption errors return nonzero exit status; failed sources stay in reports and suppress success heartbeats.
• Parallel migration tools use isolated local/S3/Drive paths. Google Drive replication uses the rclone adapter, not a native backend.

Validation: 22 Rust tests, three configuration tests, and four adapter scenarios passed locally. Real PostgreSQL/TimescaleDB recovery, storage providers and Windows replication remain to be verified on the server. Memory-bounded streaming remains pending. Publishing this release does not activate the parallel cron or retire the legacy backup scripts.

v0.1.2

Full Changelog: v0.1.1...v0.1.2

v0.1.1

Full Changelog: v0.1.0...v0.1.1

v0.1.0

Full Changelog: https://github.com/SecuryBlack/titan-vault/commits/v0.1.0