NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #2513 by repository stars
Latest stable
v0.46.0
Last release 20 days ago
02 Nov 2026
Ships fairly regularly
a new release about every 2 weeks
Nearly every release is documented
notes for 59 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
1 years old
109 releases · first in 2025
Drag across the ruler to compare, or tap a release to open it.
<!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 -->
v0.46.0
Compare
Your coding agent can read these notes before it upgrades. Set up the MCP server →
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
--log-level, and runs nothing, instead of ignoring the flags after the word, running only the first mode or falling back to INFO.--help is printed on standard output.proxsave or proxmox-backup symlinks from the directory it was started in when PATH holds a relative entry, and no longer hangs on a PATH entry that is not a directory.<<.<!-- end of auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
DAEMON_LOG_PATH; the three most recent daemon start logs are retained.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- release-tag: v0.43.0 -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Bug Fixes
Documentation
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Documentation
Bug Fixes
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
PBS_TARGET_ENABLED, PBS_TARGET_STORAGE).CLOUD_REMOTE accepts an absolute local directory.MIN_DISK_SPACE_PBS_GB for PBS free-space checks.Bug Fixes
errors_total counts the error that stopped a failed run.Security
SET_BACKUP_PERMISSIONS is set.storage.cfg and PBS password file reads confined to their directory.Documentation
Action Required
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
guards/ and restore/.Bug Fixes
Documentation
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Bug Fixes
Documentation
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
acme/accounts/.Bug Fixes
Documentation
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Bug Fixes
Documentation
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
UNKNOWN states and reasons.--dry-run when used with upgrade operations.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
READY WITH WARNING advisory.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Bug Fixes
Improvements
Removed the deprecated daemon opt-out setting. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
install.sh --upgrade.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Documentation
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
First stable of the 0.30 line. Includes everything from v0.30.0-beta1 to v0.30.0-beta11.
New Features
proxsave opens an interactive dashboard, and backup, install, upgrade and support stream inside a contained scrollable panel. The legacy wizard is gone.--daemon-status, binary-alignment checks and stuck-backup recovery.--upgrade --localfile, upgrade-beta.sh for prereleases, and a What's New screen (--show-whatsnew) shown once after an interactive upgrade.HOST_BACKUP_MODE to back up a Proxmox host from an HA-LXC appliance over a read-only mount.Bug Fixes
Security
.git/config.Documentation
Upgrade Notes
PXAR_SCAN_ENABLE=true in backup.env to keep it.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Documentation
Bug Fixes
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Tests
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
--show-whats-new mode to display release highlights and exit.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
/etc/pve bind-mount shape and stricter host-path/symlink confinement.<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Bug Fixes
Tests
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
jq.jq.Documentation
bash upgrade-beta.sh ... instead of sh upgrade-beta.sh ....
<!-- end of auto-generated comment: release notes by coderabbit.ai --><!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Bug Fixes
Security & Reliability
Tests
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Bug Fixes
Documentation
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Bug Fixes
Documentation
This is a large beta. The headline change is a completely rebuilt graphical interface, alongside a new resident daemon, per-channel Healthchecks monit
This is a large beta. The headline change is a completely rebuilt graphical interface, alongside a new resident daemon, per-channel Healthchecks monitoring, in-app upgrades, and extensive restore/backup safety fixes.
New Graphical Interface
proxsave on its own now opens an interactive dashboard (menu, diagnostics, maintenance).Ctrl+C as a global emergency interrupt, c to copy the whole stream log to the clipboard, and seamless dashboard-to-flow transitions.Resident Daemon
--daemon mode with its own scheduler and a hang watchdog.proxsave --daemon-status command plus daemon scheduler commands (install / disable / re-enable / status).Healthchecks Monitoring
In-App Upgrade
upgrade-beta.sh to install prerelease builds, and --upgrade --localfile to finalize from a local file without downloading.Support & Notifications
NOTIFY-ERR lines distinctly, and add a NotifyError severity level.Backup Output
Security & Hardening
Bug Fixes
Note
Release Date: July 20, 2026 Commit: 90338af15480d18a3eeb307e8f8a962ad5073a97
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
New Features
Bug Fixes
Tests
Upgraded Telegram setup verification to provide consistent messaging for verified, partially verified, and “upgrade required” outcomes, with improved
New Features
Bug Fixes
Documentation
dc41a38a6a71e543e417a5a658e78198000da5c4 Release v0.28.0 (#246)
Extended configurable per-syscall I/O timeout behavior across backup, restore, logging, storage, cloud, and security preflight workflows.
New Features
Bug Fixes
/tmp/proxsave and hardened related cleanup.LOG_PATH mounts.Documentation
FS_IO_TIMEOUT and profiling documentation to reflect per-syscall and /tmp/proxsave behavior.Tests
6b6bb7a794aabda4a591dbe2bf859d3e01697db1 Release v0.27.0 (#245)
Added --cleanup-guards for removing leftover restore mount guards after storage returns.
--cleanup-guards for removing leftover restore mount guards after storage returns.proxsave binary and clarified cleanup-guard semantics.Release pipeline helpers and post-merge/tag intake workflows; added concurrency gating for releases
Added support for additional network backends (Netplan, systemd-networkd, NetworkManager) and improved cloud backup discovery via manifest files.
New Features
Bug Fixes
Security & Hardening
Documentation
Tests
59eb7b04bc4ebbd87ea1001f2d9138ad809a4665 Security hardening and audit correctness fixes (gosec + bug report) (#234)
Added ECDSA P-256 release signature verification for enhanced security; install.sh and proxsave --upgrade now validate release authenticity before ins
New Features
install.sh and proxsave --upgrade now validate release authenticity before installation.--env-migration tooling for migrating legacy backup.env configurations to Go.Bug Fixes
Documentation
--env-migration.Chores
Nothing published for this version
This PR addresses PXAR parallel collection isolation, improves manifest error reporting, expands test coverage, and hardens the CI pipeline. It touche
This PR addresses PXAR parallel collection isolation, improves manifest error reporting, expands test coverage, and hardens the CI pipeline. It touches three functional areas: the backup collection layer, the orchestrator's legacy metadata parsing, and GitHub Actions workflow hardening.
runPBSPXARStep no longer cancels the shared context on the first per-datastore error; it now collects all per-datastore failures with errors.Join and the new handlePBSPXARStepError helper treats datastore errors as best-effort warnings unless the parent context itself is done.LoadManifest now surfaces both the JSON parse cause and the legacy parse cause in its combined error message; parseLegacyMetadata now propagates bufio.Scanner errors instead of silently succeeding.inspectRcloneMetadataManifest in decrypt.go now handles BACKUP_TARGETS, PROXMOX_TARGETS, PROXMOX_VERSION, PVE_VERSION, and PBS_VERSION fields with deduplication logic for targets.Bug Fixes
Tests
Chores
Email delivery method now supports additional alias values (proxmox, proxmox-notifications, proxmox-mail-forward) for PMF delivery.
New Features
proxmox, proxmox-notifications, proxmox-mail-forward) for PMF delivery.Bug Fixes
Tests
Chores
24b4c96cf24a0757b0eff46495b11923302b2aaf Stabilize notifier dispatch, CI, and cleanup refinements (#216)
Base directory is now auto-detected from the installed executable; BASE_DIR environment variable is no longer user-configurable and will be ignored.
New Features
BASE_DIR environment variable is no longer user-configurable and will be ignored.Bug Fixes
Documentation
Added smart filesystem merge during restore with user confirmation.
New Features
Bug Fixes & Improvements
Infrastructure
Safer command execution preventing injection vulnerabilities.
New Features
Bug Fixes
Documentation
Tests
Chores
Hybrid Proxmox support: VE+PBS detection with separate PVE/PBS version reporting and explicit backup-targets.
New Features
Bug Fixes
Improvements
Enhanced backup candidate display with detailed metadata presentation including hostname, backup mode, tool version, target configuration, and compres
New Features
Tests
Chores
Enhanced email relay troubleshooting with clearer failure guidance and configuration details.
New Features
Bug Fixes
Documentation
🧭 Unified installer semantics, context-aware TUI flows, and safer atomic restore/write paths
🧭 Unified installer semantics, context-aware TUI flows, and safer atomic restore/write paths
This release is a broad quality and safety upgrade across ProxSave’s interactive workflows (CLI + TUI). It aligns installer and new-install behavior across entrypoints, makes TUI execution fully context-aware (cancellation and timeouts work end-to-end), hardens several file operations with atomic writes/extraction, and improves correctness in storage usage reporting and notification defaults. It also substantially expands test coverage (including true end-to-end decrypt TUI coverage) and reduces flakiness across CI.
Installer parity (CLI + TUI): one set of rules, everywhere
backup.env handling aligned with four explicit actions: Overwrite, Edit existing, Keep existing & continue, and Cancel (same semantics in CLI and TUI).--new-install confirmation flow aligned via a shared reset plan and a single source of truth for preserved entries (build/env/identity). CLI confirmation is CLI-only; TUI confirmation is a pure adapter.SECONDARY_ENABLED=false, SECONDARY_PATH=, SECONDARY_LOG_PATH=SECONDARY_LOG_PATH optional,Decrypt workflow consistency + true end-to-end TUI coverage
"0" is now an explicit abort in both CLI and TUI, with clear messaging and ErrDecryptAborted mapping."0" token check).Context-aware TUI across the board (cancellation and timeouts now “just work”)
App.RunWithContext(ctx) and migrated wizard runners and orchestrator prompts to honor context cancellation/timeouts.context.Background() in modals).DetectWithContext, immutable attribute ops, identity writes, base-dir resets) using exec.CommandContext and ctx.Err() checks.Safety and correctness hardening (atomic operations + better error handling)
CreateTemp in the target directory to avoid ENAMETOOLONG collisions while preserving atomic rename semantics.Close() calls while preserving explicit close error reporting..bak-* at commit time,Security and integrity improvements
Lstat,os.SameFile() between Lstat and the opened file,chmod/chown) only after SameFile validation.tview.Escape across screens, prompts, and headers to prevent markup interpretation.Storage reporting and retention correctness
Blocks - Bfree, not Total - Bavail) so reserved blocks aren’t misreported as “used”.RETENTION_DAILY <= 0 consistently yields an effective daily minimum of 1 across all paths (prevents misclassification/deletion).*.bundle.tar.bundle.tar, and prevented duplicate cloud uploads when a bundle exists.Notification config defaults + legacy compatibility
EMAIL_ENABLED now defaults to false when unset.*_ENABLE env flags (including env override precedence) and added missing Gotify overrides.Robustness, UX, and test reliability
../ traversal escaping the test root.t.Setenv for safer cleanup and reduced flakiness.Dependencies
golang.org/x/crypto to 0.49.0.Behavior changes to note:
SECONDARY_ENABLED=true, and disabling secondary always clears saved secondary paths."0" as an explicit abort consistently in CLI and TUI.EMAIL_ENABLED defaults to false when unset; legacy *_ENABLE aliases remain supported and now override canonical settings consistently.Overall: a more predictable installer (one shared decision model), fully context-aware TUI workflows, safer atomic restore/write behavior, and stronger correctness/security guarantees—backed by substantially expanded and stabilized test coverage.
🛡️ Restore integrity enforcement, symlink/path hardening, and bounded IO for safer recovery
🛡️ Restore integrity enforcement, symlink/path hardening, and bounded IO for safer recovery
This release significantly strengthens restore/decrypt safety and integrity. It hardens decision-making against untrusted metadata, enforces checksum verification before any restore/decrypt proceeds, and closes multiple symlink and path-validation bypasses (including staged apply overlays). It also bounds filesystem and input timeout wrappers to prevent goroutine buildup, improves PBS override handling and output key disambiguation, and delivers major test coverage expansion (including ~99% coverage for network rollback/apply logic).
Restore integrity: checksum verification is now mandatory
Restore planning hardening: trust archive-backed facts, not spoofable metadata
Symlink + path security: close escape/bypass classes across restore and staged apply
Resource safety and robustness: bounded IO/timeouts and race fixes
Backup output safety: sanitize path segments to prevent traversal/collisions
PBS datastore overrides: safer semantics and collision-proof output keys
PBS_DATASTORE_PATH overrides while preserving existing names for real CLI-discovered datastores.PBS_DATASTORE_PATH overrides (warn + skip).Network and restore UX/test reliability
Compatibility and correctness fixes
CI, build, and maintenance
Overall: materially safer restores and decrypts (integrity required, spoof-resistant decisions), hardened symlink/path handling across restore and staged apply, bounded IO/input wrappers to prevent resource buildup, and improved PBS override safety and observability with strong regression coverage.
📨 Telegram pairing in the installer, non-interactive upgrade confirmations, and improved privilege-context detection
📨 Telegram pairing in the installer, non-interactive upgrade confirmations, and improved privilege-context detection
This release improves first-time setup and automation by adding an optional Telegram pairing step to the installer, enabling non-interactive upgrade confirmations, and expanding privilege-context detection so limited-privilege environments are identified once at startup and reused consistently by collectors.
Installer: optional Telegram pairing (CLI + TUI):
notify.CheckTelegramRegistration.Upgrades: non-interactive auto-confirm support:
--upgrade flow can now be auto-confirmed by passing a trailing y (example: --upgrade y).Args.UpgradeAutoYes and extractUpgradeAutoYesArgs to preprocess os.Args; parser updated accordingly.Privilege context: earlier detection + broader limited-privilege coverage:
Privilege context: ...) with full evidence in DEBUG./proc.Overall: smoother Telegram setup, easier scripted upgrades, and more accurate, consistent behavior in containerized or otherwise constrained environments.
🧪 Installer UX upgrades, optional post install audit, and major testability expansion across restore paths
🧪 Installer UX upgrades, optional post install audit, and major testability expansion across restore paths
This release focuses on making installation and upgrades easier to operate while greatly expanding unit test coverage for critical restore workflows. It adds a guided post install audit that can disable unused collectors, improves the TUI wizard when editing existing configs, removes obsolete legacy compatibility layers, and introduces extensive dependency injection hooks so mount guards, firewall, access control, NIC mapping, and PBS staged apply can be tested thoroughly without touching the real system.
Installer and wizard improvements
Optional post install audit using dry run
Removal of obsolete legacy compatibility
Major restore testability and coverage expansion
Dependencies
Behavior changes to note
Overall: a much smoother install experience, an optional guided audit to keep configs lean, and significantly stronger regression protection for the riskiest restore paths through deep testability improvements.
🧷 Rootless-friendly collection: privilege-sensitive failures become SKIPs (with clearer hints)
🧷 Rootless-friendly collection: privilege-sensitive failures become SKIPs (with clearer hints)
dmidecode, blkid, sensors, and smartctl as SKIPs when matching expected permission patterns, reducing false-positive noise in constrained environments./proc/self/{uid_map,gid_map} and /run/systemd/container, plus a deps hook for overrides; expanded unit tests for detection and failure matching.Overall: cleaner logs and more predictable behavior when running ProxSave in rootless or user-namespace environments, without masking genuinely actionable issues.
Removed deprecated PXAR tuning options and related code paths/fields from CollectorConfig.
🧭 PBS API-first restores, chunked artifacts, safer staging, and bounded IO across backups/restores
This release is a major step forward in restore safety, scalability, and operator control. It introduces an API-first, UI-driven PBS staged restore flow (with explicit Merge vs Clean behavior), adds chunking + reassembly to handle large artifacts and improve selective restores, hardens restore staging directory lifecycle and permissions, and makes several key operations cancellable and bounded (streaming category analysis, PVESH timeouts, filesystem IO timeouts). It also improves compatibility diagnostics, rollback handling, and test robustness.
PBS staged restore: API-first + UI-driven reconciliation (Merge vs Clean 1:1):
notifications.cfg / notifications-priv.cfg and a generated notifications_summary.json.proxmox-backup-manager) with strict 1:1 reconciliation support and controlled fallbacks.backup.env and into an interactive restore-time choice:
Chunking + reassembly for large artifacts (and better selective restore matching):
.chunked markers) and robust chunk write logic.ReassembleChunkedFiles after extract:
chmod/chown/mtime, and restores metadata.originalPathFromChunk) to reduce missed matches.Backup prefiltering + structured-config safety (less damage, better stats):
/etc/proxmox-backup, /etc/pve, /etc/ssh, /etc/pam.d, /etc/systemd/system.(changed bool) and normalization is limited to safe text normalization (no sorting).datastore.cfg:
pbs_datastore_inventory.json using a lightweight inventory parser.prefilter-manual CLI command to run the prefilter standalone (custom root/max-size/log-level).Restore staging dirs: secure lifecycle, cleanup, and safer defaults:
/tmp/proxsave/restore-stage-*:
0700 permissions, PID-aware naming, unique creation via MkdirTemp with timestamp/pid pattern.cleanupOldRestoreStageDirs() and wired it into orchestrator startup/UI paths to remove aged staging dirs.PROXSAVE_PRESERVE_RESTORE_STAGING and preserve-on-warnings behavior (including staged installs/network), plus auto-removal after successful clean restores.Streamed + cancellable category analysis with safe fallback:
AnalyzeBackupCategories now accepts a context and scans archives streaming (O(1) memory), enabling cancellation and better error handling.Broader context cancellation support and restore code hardening:
ctx.Err() checks in long-running loops (backup history/replication aggregation) for early cancellation.contextReader) so large io.Copy operations can be cancelled cleanly.PVE service management and restore ordering correctness:
pvestatd → pveproxy → pvedaemon → pve-cluster), start uses forward order.Security hardening and rollback artifact robustness:
Compatibility messaging, warnings, and UX improvements:
ValidateCompatibility now produces clearer warnings/errors when backup/system type cannot be detected (includes type info where available).logger.HasWarnings()), with unit test coverage.len(selected).logStep messages to include step index for clearer progress tracing.Bounded execution to avoid hangs: PVESH and filesystem IO timeouts:
PVESH_TIMEOUT and applied per-call timeouts to pvesh operations.active, enabled, status) with tolerant parsing of bool/int/string forms:
FS_IO_TIMEOUT and a new internal/safefs bounded probe layer (stat, readdir, statfs) to avoid blocking on unreachable mounts.pvesh context cancellation handling and tightened deps signatures for command/run/lookpath to accept contexts/timeouts.Collector refactor: bounded filesystem sampler replaces legacy PXAR sampling:
fs_sampling_bounded).CollectorConfig.Lock-file correctness and CI hygiene:
killFunc), and remove stale locks when appropriate.--progress artifact; removed stale artifacts before runs.--) to avoid accidental writes.Build/versioning improvements:
.dirty handling) for both build and build-release.Dependencies:
golang.org/x/term to 0.40.0.golang.org/x/crypto to 0.48.0.Breaking/behavior changes to note:
RESTORE_PBS_APPLY_MODE / RESTORE_PBS_STRICT settings were removed.Overall: more reliable PBS restores (API-first with explicit operator intent), better handling of large artifacts via chunking, safer staging with stronger permissions and cleanup, and fewer hangs thanks to bounded IO and cancellable workflows.
Nothing published for this version
🧱 Quieter PVE ACL logging, atomic staged restores, and more reliable tests
🧱 Quieter PVE ACL logging, atomic staged restores, and more reliable tests
BACKUP_PVE_ACL (users/roles/groups/ACL; domains/realms optional) and made domains.cfg optional so it’s not warned/counted as missing on default standalone PVE installs.fs_atomic) and switched staged-apply paths (network, PBS, PVE, firewall, HA, notifications) to write atomically while enforcing final ownership/permissions (avoids umask-related issues). Removed duplicate atomic write implementation.root:root group regressions) with additional unit tests and updated docs.writeFileAtomic now fsyncs file data and fsyncs the parent directory (treating unsupported dir fsync as non-fatal). Added a safe default case in rclone discovery to skip unsupported switch branches.CheckerConfig, avoid repo lock-file reliance, and include better cleanup. Added FS operation hooks to make atomic-write tests hermetic without requiring root..backup.lock metadata.Overall: cleaner PVE ACL reporting, safer staged restores via durable atomic writes with correct ownership, and a sturdier, less flaky test suite.
🧩 Config var expansion, clearer docs, and correct PVE ACL collection
🧩 Config var expansion, clearer docs, and correct PVE ACL collection
${VAR} / $VAR expansion for scalar config values (config keys first, then environment) with caching + cycle protection; preserves historical BASE_DIR behavior. Includes unit tests.backup.env values are resolved by ProxSave without requiring export.user.cfg), updated collector logic and tests accordingly.Overall: more flexible configuration, clearer guidance, and more accurate PVE ACL handling.
…improves PVE manifest/cluster handling, prunes deprecated env keys during upgrades, and refines restore interaction and network rollback UX for more r…
🧰 More granular collectors, clearer end-of-run summaries, and safer restore UX refinements
This release tightens operational clarity and configurability across backup and restore workflows. It adds issue capture with end-of-run summaries, introduces finer PBS collection toggles with clearer logging, improves PVE manifest/cluster handling, prunes deprecated env keys during upgrades, and refines restore interaction and network rollback UX for more reliable operation on constrained terminals (IPMI/serial). It also improves notifier ergonomics with automatic email recipient detection and bumps the Go toolchain.
populatePVEManifest now always initializes the manifest and uses structured logging options for consistent, descriptive output.BACKUP_* flags.BASE_DIR and CRON_* from generated backup.env (BASE_DIR is auto-detected; cron is managed via crontab).BASE_DIR, CRON_SCHEDULE, CRON_HOUR, CRON_MINUTE), emits a warning, and avoids rewriting unless missing keys were added or deprecated lines were removed.UpgradeResult is now fully populated (MissingKeys, ExtraKeys, CaseConflictKeys, PreservedValues, Warnings) for consistent caller behavior.suppressPVEChecks for cluster restores to skip PVE-specific health checks and adjust network health options.applyNetworkWithRollbackWithUI now returns a constructed NetworkApplyNotCommittedError for richer downstream reporting.ReadLineWithContext directly, avoiding carriage-return update issues on IPMI/serial consoles while preserving timeout/cancel behavior.root@pam across Proxmox platforms:
pvesh first, fall back to pveum / proxmox-backup-manager, and finally parse user.cfg from PVE/PBS locations.Config.parse.Overall: more configurable backups (especially PBS), clearer and more actionable run summaries, cleaner env upgrades with deprecated-key pruning, and a more robust restore/operator experience—especially on real-world consoles and clustered restores.
🧩 Cleaner config upgrade diffs, smarter key insertion, and clearer upgrade reporting
🧩 Cleaner config upgrade diffs, smarter key insertion, and clearer upgrade reporting
This maintenance release improves the configuration upgrade experience by making upgrades more readable and less disruptive: missing template keys are inserted in a way that respects the user’s existing ordering, unanchored keys are grouped into a dedicated upgrade section, and upgrade results expose clearer summaries (including case-only conflicts). It also improves operator visibility by logging exactly which keys were added, and completes additional Italian → English comment/template text translations.
cfgUpgradeResult.MissingKeys).parseEnvValues records per-key source ranges and computeConfigUpgrade builds ordered insert operations (sorted) to merge template lines into the original file with minimal diffs.# Added by upgrade section (with appropriate spacing) instead of being inserted arbitrarily.CaseConflictKeys to the upgrade result and preserved case-conflict keys in place instead of treating them as extra keys.MissingKeys is now always populated (empty slice when none are missing) to avoid inconsistent result handling by callers.backup.env template comments), with no functional behavior changes.Overall: config upgrades are now more predictable and operator-friendly—minimal diffs, stable ordering, clearer summaries (including case conflicts), and better post-upgrade visibility of what changed.
🧾 Config upgrade fidelity, comment/case preservation, and actionable upgrade warnings
🧾 Config upgrade fidelity, comment/case preservation, and actionable upgrade warnings
This fix release hardens the backup.env parsing and upgrade pipeline to be much more faithful to real-world configs. It improves handling of comments (inline and block), key casing, legacy export prefixes (with arbitrary whitespace), and multiline values, while adding non-fatal warnings that surface potential issues during plan/upgrade runs. The result is safer upgrades with fewer surprises and clearer operator feedback.
SetEnvValue):
export token, normalizing whitespace (e.g. export FOO=...) instead of dropping it.parseEnvFile/parseEnvValues now ignores comment-only lines inside multiline block values, and stores comment text alongside parsed values.splitKeyValueRaw handles legacy export prefixes, extracts quoted/unquoted values more robustly, and returns parsed inline comments.computeConfigUpgrade uses case-insensitive lookups, tracks processed user keys, preserves original user casing for extra keys, and counts preserved values correctly.Warnings []string to the upgrade result and propagated warnings end-to-end so they print during plan/upgrade operations.KEY=VALUE lines (multiline behavior preserved).FindInlineCommentIndex, FindClosingQuoteIndex, SetEnvValue) to centralize handling of inline comments, escaped #, and quoted values.setEnvValue implementations to use the unified utility function across the codebase.export whitespace edge cases fixed:
export\t\tKEY=... works correctly and keys like exporter=... are not misidentified.# cases).Overall: config upgrades are now safer and more predictable—comments and formatting are preserved, casing and legacy export syntax are handled correctly, and potential pitfalls are reported as clear, non-fatal warnings.
🛠️ Smarter config upgrades, machine-readable upgrade output, and clearer upgrade UX
🛠️ Smarter config upgrades, machine-readable upgrade output, and clearer upgrade UX
This patch release focuses on upgrade-time correctness and operator clarity, improving how backup.env is upgraded during binary upgrades. It adds a machine-readable JSON mode for config upgrades, wires automatic template-key merging into the upgrade flow, hardens multi-line env parsing/rendering, and refines prompts, previews, and error reporting for easier troubleshooting.
backup.env, adding missing keys while preserving existing values.--upgrade-config-json to emit structured config-upgrade results suitable for automation and tooling, with robust error handling and diagnostics.parseEnvValues, splitKeyValueRaw, renderEnvValue, findClosingQuoteLine) and updated computeConfigUpgrade to maintain fidelity of complex env structures.backup.env may be updated; printUpgradeFooter reports detailed upgrade outcomes or errors.Overall: safer and more transparent upgrades, better automation support via JSON output, and correct handling of complex backup.env values.
🧭 Major restore/category overhaul, staged SAFE-apply expansion, and storage/mount-guard hardening
🧭 Major restore/category overhaul, staged SAFE-apply expansion, and storage/mount-guard hardening
This is a major release that significantly evolves both backup layout and restore capabilities. It introduces a broader staged-apply model (especially for access control and notifications), adds new transactional and rollback-protected restore paths (firewall/HA), hardens storage safety with mount guards and smarter /etc/fstab handling (including stable device remapping), and makes backup collection more configurable via feature-based and pattern-based exclusions. Diagnostics are also centralized and the overall UX/logging is clearer and safer.
pbs_remotes, maintenance_pbs, and updated pbs_config to export-only (explicitly never writing full /etc/proxmox-backup back to the system; subsets are applied via staged categories).root@pam safety rails and ensuring root@pam keeps Admin on /.root@pam and its tokens/TFA from the fresh install for safety.pve_ha category with staged logic, rollback timer, confirmation workflow, and HA rollback backup integration.pve_sdn) with apply functions wired into the restore workflow.--cleanup-guards mode (with validation against conflicting flags) and a testable cleanup implementation that safely handles hidden/overmounted guards./etc/fstab restore with stable device remapping:
/dev/* references to UUID/PARTUUID/LABEL using collected inventory (blkid/lsblk JSON/PBS inventory).var/lib/proxsave-info/ and removed legacy scattered output directories./home/* under ./home/<user> (avoids restoring into legacy /users/... paths).storage_stack, user_data, proxsave_info export-only) and added glob support for category path matching (e.g. auto.*).datastore.cfg, user.cfg, remote.cfg, sync.cfg, etc.) and logs per-file collection status.FilesNotFound / FilesSkipped counters and richer status reporting for skipped config paths.pbs_host and pbs_tape, expanded datastore_pbs to include s3.cfg, and aligned categories/docs.proxy.cfg) and SSL assets (proxy.pem, proxy.key, ssl/) with updated tests/docs.network + ssl and warnings about hostname/origin changes.RCLONE_TIMEOUT_CONNECTION as per-command during scanning (timer resets per rclone lsf/cat).main.go (more visible Info-level messages)./etc/crypttab), and referenced keys.fetch/download) using curl/wget and made GitHub release tag fetch more robust (prefer jq with regex fallback).github.com/gdamore/tcell/v2 to 2.13.8, golang.org/x/term to 0.39.0, golang.org/x/crypto to 0.47.0, and golang.org/x/text to 0.33.0.context.DeadlineExceeded (with tests) instead of mapping deadlines to abort errors./proc/self/mountinfo path unescaping with manual octal decoding, out-of-range preservation, and thorough unit tests.Overall: a big step forward in restore safety and capability—new staged/transactional workflows, safer access control handling, mount-guarded storage restores, smarter fstab recovery, a cleaner backup/category layout, and stronger exclusions, diagnostics, and test coverage.
One column per month.