Skip to content

CHANGELOG.md

Latest commit

 

History

History
902 lines (732 loc) · 34.5 KB

CHANGELOG.md

File metadata and controls

902 lines (732 loc) · 34.5 KB

Changelog

All notable changes to Nimbus Backup (GUI) will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

[0.2.12] - 2026-03-23

Fixed

  • Better responsive design for very small screens - Improved approach for low-res displays
    • Reduced MinWidth from 600 to 400 (supports 800x600 and smaller screens)
    • Reduced MinHeight from 500 to 300 (supports low-resolution displays)
    • Added compact text mode for buttons on screens <480px
    • Button text adapts: "One-shot (maintenant)" → "Now" on small screens
    • Works on VM displays, low-res screens, and Proxmox VE console

Improved

  • Truly responsive UI that adapts to any screen size
  • No forced minimum that could exceed screen resolution

[0.2.11] - 2026-03-23

Fixed

  • UI overflow on small screens - Window too small causes UI elements to be cut off
    • Added MinWidth: 600 and MinHeight: 500 to Wails window options
    • Prevents close button from being inaccessible
    • Prevents buttons and content from overflowing
    • Ensures all UI elements remain visible and usable

Improved

  • Better UX on small screens and low-resolution displays

[0.2.10] - 2026-03-23

Fixed

  • MSI build error - Incorrect service exe path in Product.wxs
    • Changed path from ../../cmd/service/ to ../../gui/build/bin/
    • Workflow builds service to gui/build/bin/NimbusBackupSVC.exe
    • Fixes "LGHT0103: The system cannot find the file"

[0.2.9] - 2026-03-23

Fixed

  • Service build error - app.App missing BackupHandler interface methods
    • Implemented all 6 required methods as stubs (StartBackup, GetConfigWithHostname, etc.)
    • Fixes "*app.App does not implement api.BackupHandler"

[0.2.8] - 2026-03-23

Fixed

  • GUI build error - Missing gui/api in go.mod
    • Added gui/api to require and replace directives
    • Fixes "module @latest found, but does not contain package gui/api"

[0.2.7] - 2026-03-23

Fixed

  • Missing gui/api/go.mod - Service build error
    • Created gui/api/go.mod module definition
    • Fixes "reading go.mod: file not found" error

[0.2.6] - 2026-03-23

Fixed

  • Service build error - "gui is a program, not an importable package"
    • Extracted App struct to new gui/app package
    • Service now imports gui/app instead of gui (package main)
    • Created gui/app/go.mod as separate module
    • Core methods implemented as stubs (CleanupAbandonedJobs, StartScheduler, StopScheduler)

Technical

  • New package:
    • gui/app/ - Importable package with App logic
    • gui/app/app.go - App struct and service methods
    • gui/app/go.mod - Separate module definition
  • Modified files:
    • cmd/service/main.go - Import gui/app instead of gui
    • cmd/service/go.mod - Updated dependencies (gui/app, gui/api)

Note

Full App implementation will be migrated from gui/main.go to gui/app in future commits. Current version uses minimal stubs to unblock service build.

[0.2.5] - 2026-03-23

Note

  • Re-release of v0.2.4 with proper build sequence
  • All functionality identical to v0.2.4
  • Fixes tag timing issue

[0.2.4] - 2026-03-23

Fixed

  • Service build error - Missing replace directives in cmd/service/go.mod
    • Added replace directives for all local modules (clientcommon, pbscommon, retry, security, snapshot)
    • Paths adjusted relative to cmd/service/ directory
    • Fixes CI error: "malformed module path: missing dot in first path element"
    • Service now builds successfully in GitHub Actions

Technical

  • Modified files:
    • cmd/service/go.mod - Added replace directives with relative paths
    • Local modules now properly resolved during go mod tidy

[0.2.3] - 2026-03-23

Changed

  • Release notes consolidation - Complete release notes since v0.2.0
    • Added comprehensive feature summary for v0.2.0 → v0.2.3
    • Detailed statistics and examples showing impact of each feature
    • Migration notes for v0.1.x → v0.2.x upgrades
    • Backup strategy recommendations (file-mode vs disk-mode)
    • Before/after comparisons for major fixes

Documentation

  • RELEASE_NOTES.md - Major restructuring with complete v0.2.x summary
    • Architecture changes (binary separation, HTTP API)
    • Long backup reliability (keep-alive fix)
    • Auto-split feature (large backups >100GB)
    • Smart system exclusions (VSS snapshots, paging files)
    • Real-world examples and statistics

[0.2.2] - 2026-03-23

Added

  • Automatic exclusion of Windows system folders - File-mode backups now skip system folders

    • System Volume Information (VSS snapshots storage - can be 100s of GB)
    • $RECYCLE.BIN (Windows recycle bin)
    • Recovery (Windows recovery partition data)
    • Prevents backing up VSS snapshots when selecting entire drive (e.g., D:\)
    • Case-insensitive matching for Windows compatibility
    • Skipped folders logged in backup report

  • Automatic exclusion of Windows system files

    • pagefile.sys (Windows page file)
    • hiberfil.sys (Hibernation file)
    • swapfile.sys (Windows swap file)
    • DumpStack.log.tmp (Crash dump temporary file)
    • Prevents backing up large system files that shouldn't be in backups

Fixed

  • CI/CD build error - Service executable not built before MSI creation
    • Added build step for NimbusBackupSVC.exe in GitHub Actions workflow
    • Service now built from cmd/service before WiX packaging
    • Fixed LGHT0103 error: "The system cannot find the file NimbusBackupSVC.exe"
    • Both binaries (GUI + Service) now copied to dist/ folder

Technical

  • Modified files:
    • pbscommon/pxar.go - Added shouldSkipSystemFolder() and shouldSkipSystemFile()
    • Exclusion logic in WriteDir() loop before recursing into subdirectories
    • .github/workflows/build-and-release.yml - Added service build step
    • Service built with same flags as GUI: -trimpath -buildmode=pie -ldflags "-s -w"
    • Build order: GUI → Service → MSI packaging

Important Note - File Mode Backups

When backing up an entire drive (e.g., D:\) in file mode, the backup will now automatically exclude:

  • VSS snapshot storage (System Volume Information) which can contain hundreds of GB
  • Recycle bin and recovery data
  • Large system paging files

Impact: Backup size will match actual file size instead of including hidden system data. Example: Drive shows 1.03 TB used but files are 141 GB → Backup will be ~141 GB (not 1.03 TB)

Recommendation:

  • For file-level restore: Use file mode (current behavior)
  • For bare-metal restore: Use disk mode (includes everything, requires separate job)

[0.2.1] - 2026-03-23

Added

  • Auto-split for large backups - Intelligent job splitting for backups >100GB
    • Automatically detects backup size before execution
    • Confirmation dialog shows total size and suggested split count
    • Bin-packing algorithm distributes folders into balanced jobs
    • Each job targets ~100GB max (configurable threshold)
    • Max 10 jobs per backup to prevent over-fragmentation
    • Sequential execution with per-job retry capability
    • Frontend displays progress for each split job
    • Backend analysis API: AnalyzeBackup(), CreateBackupSplitPlan()
    • Example: 864GB backup → 9 jobs of ~96GB each

Technical

  • New files:
    • gui/backup_analysis.go - Core split logic with bin-packing algorithm
    • gui/backup_split_api.go - API exposure to frontend
  • Modified files:
    • gui/frontend/src/App.jsx - Auto-detect, confirmation dialog, sequential execution
  • Constants:
    • SplitThreshold: 100GB (when to propose split)
    • MaxChunkSize: 100GB (target size per job)
    • Max 10 jobs total
  • Algorithm: First-fit-decreasing bin-packing (sorts folders by size, fills jobs sequentially)

Benefits

  • Robustness: If one job fails, only retry ~100GB instead of losing 11+ hours
  • Speed: Smaller jobs less likely to hit timeout issues
  • Transparency: User sees exactly what will be split and can confirm
  • Deduplication-friendly: PBS deduplicates at chunk level, so splitting by folder doesn't affect efficiency

User Experience

Backup volumineux détecté (864.5 GB)

Voulez-vous le découper en 9 backups ?
• Job 1: 96.2 GB (3 dossiers)
• Job 2: 95.8 GB (4 dossiers)
...
• Job 9: 94.1 GB (2 dossiers)

[Oui, découper] [Non, backup unique]

[0.2.0] - 2026-03-23

Changed

  • BREAKING: Binary separation architecture
    • GUI and Service now separate executables
    • NimbusBackup.exe - GUI application (Wails v2)
    • NimbusBackupSVC.exe - Windows Service (kardianos/service)
    • Communication via HTTP API on localhost:18765
    • Replaces previous single binary with --service flag

Added

  • HTTP API Server - Service exposes REST API for GUI communication

    • Port: 18765 (localhost only)
    • Endpoints:
      • /health - Service status check
      • /config - Get/update configuration
      • /jobs - List scheduled jobs
      • /jobs/create - Create new job
      • /jobs/update - Update existing job
      • /jobs/delete/{id} - Delete job
      • /backup/start - Execute backup immediately
    • JSON request/response format
    • Error handling with HTTP status codes

  • Single instance enforcement - Prevents multiple GUI instances

    • Windows mutex: Global\NimbusBackupGUIMutex
    • Activates existing window if already running
    • gui/single_instance_windows.go - Windows-specific implementation
    • User-friendly behavior (no error dialog, just focus existing window)

Fixed

  • Long backup reliability - Critical keep-alive timeout fix

    • Changed keep-alive interval from 5 minutes to 30 seconds
    • Prevents "dynamic writer not registered" HTTP/2 errors
    • Maintains TCP connection during local file processing pauses
    • Fixes backup failures after 11+ hours (52-second gaps)
    • Root cause: Client timeout (~50s) and firewall timeout (~60s)
    • Solution: Active keep-alive prevents both timeouts

  • MSI installer errors - Fixed WiX build issues

    • Removed problematic custom install dialog (InstallDirDlg)
    • Fixed LGHT0094: Unresolved reference to WixAction
    • Dual binary installation now works correctly
    • Auto-start registry component with default enabled
    • Service installed and started automatically

Technical

  • New files:

    • cmd/service/main.go - Standalone service entry point (200+ lines)
    • gui/api/server.go - HTTP API server implementation
    • gui/api/client.go - HTTP client for GUI→Service communication
    • gui/single_instance_windows.go - Mutex-based single instance

  • Removed files:

    • gui/service.go - Replaced by cmd/service/main.go

  • Modified files:

    • gui/backup_inline.go - Keep-alive changed to 30 seconds
    • installer/wix/Product.wxs - Dual binary installation
    • Makefile - Added service build target

  • Build process:

    all: cli gui service
service:
    cd cmd/service && go build -o ../../gui/build/bin/NimbusBackupSVC.exe

Migration Notes

  • Upgrading from v0.1.x:
    • MSI installer handles upgrade automatically
    • Old single binary replaced with two executables
    • Service automatically stopped, upgraded, restarted
    • Configuration preserved in %ProgramData%\NimbusBackup\
    • No user action required

Root Cause Analysis - Keep-alive Fix

  • Problem: Backups failed after 11 hours with "dynamic writer '1' not registered HTTP/2.0"
  • Evidence: Client logs showed 52-second gaps between chunk uploads
  • Cause 1: Client-side timeout (~50s for idle HTTP/2 connection)
  • Cause 2: Firewall timeout (~60s for idle TCP connection)
  • Trigger: Local file processing (chunking, hashing) paused uploads for >50s
  • Previous behavior: Keep-alive every 5 minutes (300s) - way too long
  • New behavior: Keep-alive every 30 seconds - well under both timeout thresholds
  • Validation: Gemini analysis confirmed dual timeout hypothesis

[0.1.32] - 2026-03-19

Fixed

  • CI/CD duplication - Désactivé trigger tags sur release.yml

    • Évite 2 pipelines simultanées sur chaque tag
    • build-and-release.yml gère tous les builds (CLI + GUI + tests)
    • release.yml disponible uniquement en manual (workflow_dispatch)

  • Build NBD final - NBD strictement Linux-only

    • Windows: directory + machine ✅ (nbd skippé)
    • macOS: directory + machine ✅ (nbd skippé)
    • Linux: directory + machine + nbd ✅

[0.1.31] - 2026-03-19

Added

  • Liens upsell Nimbus Backup - Génération de leads directement depuis l'app
    • Bouton CTA dans onglet "À propos"
    • Message conditionnel dans Config si PBS non configuré
    • Tracking UTM complet (source, medium, campaign, content)
    • Version dynamique dans paramètres UTM

Fixed

  • Build CLI macOS - NBD skip sur macOS (Linux/Windows uniquement)
    • Détection GOOS dans Makefile
    • NBD build uniquement sur plateformes supportées
    • Message clair lors du skip: "macOS not supported"

[0.1.30] - 2026-03-18

Fixed

  • Build CLI complet - Fix tous les modules CLI (directorybackup, machinebackup, nbd)
    • Retiré tous les usages de slices.Collect (Go 1.23+)
    • machinebackup: Collect keys manuellement avec make() + append()
    • nbd: Iterate directement sur map avec for range
    • Compatible Go 1.22 sur toutes plateformes (Linux, Windows, macOS)

[0.1.29] - 2026-03-18

Fixed

  • Progression qui recule - Fix calcul de progression pendant backup

    • Cause: totalSize mis à jour en arrière-plan par scan de fichiers
    • Solution: lastProgressPercent pour garantir progression monotone
    • Progression ne recule plus même si totalSize augmente
    • Example: 860MB=19.6% puis 917MB=11.7% → fixé

  • Clignotement affichage GUI - Console stable pendant backup

    • Cause: Printf dans pxar.go affichait/supprimait lignes en continu
    • Solution: Retiré tous les Printf de pbscommon/pxar.go
    • Fichiers skippés toujours trackés dans SkippedFiles + debug.log
    • Affichage GUI stable, logs détaillés dans debug.log uniquement

  • Build CLI échoue sur GitHub Actions - Compatibilité Go 1.22

    • Cause: slices.Collect nécessite Go 1.23+, workflow utilise Go 1.22
    • Solution: Remplacé maps.Keys + slices.Collect par simple boucle for
    • Retiré imports maps et slices inutilisés
    • Build CLI compatible Go 1.22+ sur toutes plateformes

Added

  • Sauvegarde des derniers chemins de backup
    • Config.LastBackupDirs stocke les répertoires utilisés
    • Auto-save après backup réussi
    • GetLastBackupDirs() pour pré-remplir la GUI
    • Évite de re-taper C:\Users, C:\Documents, etc. à chaque fois

Technical Details

  • ChunkState.lastProgressPercent garantit progression monotone
  • Printf retiré de WriteDir/WriteFile, gardé tracking SkippedFiles
  • directorybackup/main.go: simple boucle for range au lieu de slices.Collect
  • GUI OnComplete callback sauvegarde LastBackupDirs sur succès

[0.1.28] - 2026-03-18

Fixed

  • Critical file access error handling - Gracefully skip inaccessible files/directories

    • Changed file/directory access errors from fatal to warning + skip
    • Backup continues when encountering locked, permission-denied, or inaccessible files
    • Skipped files tracked and reported in backup completion message
    • Logged to debug.log with full details (first 50 shown)
    • GUI displays count: "⚠️ N fichiers/dossiers ignorés"
    • Fixes "The system cannot access the file" crashes

  • HTTP/2 transport cleanup improvements - More thorough connection recycling

    • Explicitly close http2.Transport connections, not just http.Client
    • Nil out old transport to force garbage collection
    • Ensures fresh connection state on every Connect() call
    • Reset SkippedFiles list on each new backup
    • Fixes persistent 400 errors when retrying after failed backup

Added

  • Skipped files reporting
    • PXARArchive.SkippedFiles tracks all skipped paths with reason
    • PBSClient.SkippedFiles accumulates skipped files across multiple archives
    • Completion message includes count and warning
    • Debug log shows detailed list (first 50 items)
    • Format: "Cannot open file: [path] (Error: [reason])"

Technical Details

  • WriteDir() and WriteFile() log access errors as warnings, return nil to continue
  • Skipped files collected in archive.SkippedFiles array
  • Transferred to client.SkippedFiles after each archive completion
  • HTTP/2 transport explicitly type-cast and closed before replacement
  • Old transport set to nil to prevent connection reuse

Root Cause Analysis

Bug #1 - File Access Crashes:

  • Backup progressed until hitting inaccessible file → crash
  • Examples: VSS snapshot directories, locked system files, permission-denied AppData files
  • Junction point skipping (v0.1.26) wasn't enough - needed graceful error handling for ALL file access errors
  • Solution: Skip any file that fails to stat/open, log it, report it, continue backup

Bug #2 - HTTP/2 Connection State:

  • After failed backup, HTTP/2 connection left in bad state
  • Next Connect() called CloseIdleConnections() but didn't fully reset transport
  • Active/broken connections not properly closed
  • Result: second backup attempt gets 400 Bad Request from PBS

[0.1.27] - 2026-03-18

Fixed

  • Build error - Removed unused encoding/json import
  • HTTP/2 connection cleanup - Close idle connections before reconnecting
    • Prevents reusing stale/broken connections from failed backups
    • Calls CloseIdleConnections() in Connect() before creating new client
    • Fixes intermittent backup failures when retrying after errors

Technical

  • Added connection cleanup to prevent state pollution between backup attempts
  • Ensures each Connect() call starts with fresh HTTP/2 connection
  • Addresses issue where first backup might work but subsequent fail

[0.1.26] - 2026-03-18

Fixed

  • Junction point handling - Critical fix for Windows backup failures
    • Added detection of junction points/symlinks using os.Lstat()
    • Automatically skip junction points with log message
    • Prevents "access denied" errors on system symlinks
    • Fixes backup failures introduced in v0.1.0 error handling refactor

Technical Details

  • Windows junction points (Application Data, Local Settings, etc.) are now detected and skipped
  • Uses os.ModeSymlink check to identify reparse points
  • Logs skipped paths: "Skipping junction point/symlink: [path]"
  • Returns nil error to continue backup without failing
  • Restores v0.0.23 behavior (skip junction points) with proper logging

Root Cause Analysis

  • v0.0.23: Junction point errors silently ignored → backup succeeds
  • v0.1.0 (commit 756da98 @ 09:20): Error handling added → backup fails on junction points
  • v0.1.26: Smart detection + graceful skip → backup succeeds with transparency

[0.1.25] - 2026-03-18

Fixed

  • Version always showing "dev" - CRITICAL FIX
    • os.ReadFile("wails.json") doesn't work in compiled binary
    • wails.json is not embedded in the executable
    • Hardcoded version in main.go until ldflags injection is configured
    • Now shows correct version "0.1.25" in About screen

Technical

  • Removed runtime wails.json reading (file doesn't exist in binary)
  • Hardcoded appVersion = "0.1.25" in main.go
  • Future: Use wails build -ldflags to inject version at compile time

[0.1.24] - 2026-03-18

Added

  • Comprehensive debug logging for CreateDynamicIndex
    • Logs archive name, BaseURL, request URL
    • Shows all request headers
    • Logs response status, proto, and body
    • Detailed error messages with error types
    • Will reveal if HTTP/2 client is working after upgrade

Debugging

  • Hypothesis: Connect() succeeds but CreateDynamicIndex fails
  • Error "HTTP request failed Post /dynamic_index" comes from line 274
  • This means pbs.Client.Do() is failing, not PBS returning 400
  • Logs will show exact failure point

[0.1.23] - 2026-03-18

Fixed

  • Version display hardcoded in frontend
    • Version was hardcoded as "0.0.16" in App.jsx line 670
    • Added GetVersion() backend function to read from wails.json
    • Frontend now dynamically loads and displays correct version
    • About screen will now show actual version (0.1.23)

Technical

  • Added App.GetVersion() method in main.go
  • Frontend calls GetVersion() on mount
  • Version state stored in React component

[0.1.22] - 2026-03-18

Added

  • Comprehensive debug logging for PBS HTTP/2 upgrade
    • Logs full HTTP request sent to PBS (all headers)
    • Logs full HTTP response received from PBS
    • Shows exact request/response for debugging 400 errors
    • Will reveal what PBS is rejecting in the upgrade request

Debugging

  • Request and response now logged with clear delimiters
  • Should show exactly what's different between v0.0.23 and v0.1.x
  • Check debug log for "=== SENDING HTTP REQUEST TO PBS ===" sections

[0.1.21] - 2026-03-18

Fixed

  • HTTP/1.1 Host header missing - PBS returned 400 Bad Request
    • Added required Host header to upgrade request (line 565)
    • HTTP/1.1 spec requires Host header, PBS enforces it strictly
    • This was the root cause of authentication failures in v0.1.x
    • Request was malformed, not an authentication issue

Root Cause Analysis

  • v0.1.20 revealed actual error: "400 Bad Request Content Type application/json"
  • Manual HTTP/1.1 upgrade request was missing Host header
  • PBS rejected the malformed request before authentication
  • Now sends: Host: [hostname]:[port] before Authorization header

[0.1.20] - 2026-03-18

Fixed

  • CRITICAL: PBS authentication error now shows real HTTP response
    • AuthErr struct modified to capture StatusCode and ResponseBody
    • DialTLSContext function (line 587-594) now passes actual PBS error details
    • Replaces generic "Authentication error" with detailed message
    • Will reveal actual HTTP status code and PBS error message
    • Bug existed since HTTP/2 upgrade implementation
    • This should finally show why backups fail after connection test succeeds

Debugging

  • Previous behavior: Printed PBS response to stdout (invisible), returned generic error
  • New behavior: Captures and returns "PBS authentication failed: HTTP [code] - [response]"
  • Will help identify if issue is HTTP/2 upgrade, authentication, or PBS server-side

[0.1.19] - 2026-03-18

Fixed

  • Build error - Removed remaining errors.New reference
    • Line 370 still had errors.New after import removal
    • Changed to fmt.Errorf("%s", errMsg)
    • All CI/CD pipelines now passing

[0.1.18] - 2026-03-18

Fixed

  • Critical bug in PBS error handling - Fixed nil error return in CreateDynamicIndex
    • When PBS returns HTTP error, the function was returning nil instead of actual error
    • Bug existed since original code but was silently masking PBS authentication errors
    • Now returns: fmt.Errorf("PBS returned HTTP %d: %s", statusCode, responseBody)
    • Added defer resp2.Body.Close() to prevent resource leak
    • Will now show exact HTTP status code and PBS error message

Changed

  • Improved error messages - SA1006 compliance with better error context
    • Changed errors.New(errMsg) to fmt.Errorf("%s", errMsg)
    • Maintains format safety while providing better stack traces

Debugging

  • This version will reveal the real PBS error that was previously hidden
  • Check logs for actual HTTP status code (401/403/500)
  • Will help identify if issue is credentials, permissions, or server-side

[0.1.17] - 2026-03-18

Fixed

  • All SA1006 linting errors resolved - Changed fmt.Errorf(variable) to errors.New(variable)
    • backup_inline.go:306 - fmt.Errorf(errMsg) → errors.New(errMsg)
    • backup_inline.go:349 - fmt.Errorf(errMsg) → errors.New(errMsg)
    • backup_inline.go:370 - fmt.Errorf(errMsg) → errors.New(errMsg)
    • Added "errors" package import

Code Quality

  • 100% lint compliance achieved ✅
    • Zero SA1006 warnings
    • Zero errcheck warnings
    • GitLab CI passing (golangci-lint v1.64)
    • GitHub Actions should now pass

Technical

  • Using errors.New() instead of fmt.Errorf() for pre-formatted error messages
  • Prevents % interpretation in error strings

[0.1.16] - 2026-03-18

Fixed

  • CI/CD linting - Direct golangci-lint execution for better error reporting
    • Replaced golangci-lint-action with direct installation
    • Action was forcing github-actions format, ignoring .golangci.yml
    • Now uses line-number format from config
    • File:line will finally be displayed for SA1006 errors

Code Quality

  • Better lint error diagnostics
  • Proper config file respect in CI

[0.1.15] - 2026-03-18

Fixed

  • Error handling - Fixed 6 errcheck linting errors
    • config_test.go: Check os.Setenv return values (4 occurrences)
    • main.go: Check logFile.Close() and f.Close() return values
    • All deferred calls now properly handle error returns

Code Quality

  • Improved error handling patterns
  • Better resource cleanup in deferred functions
  • Zero errcheck warnings

[0.1.14] - 2026-03-18

Fixed

  • Lint error reporting - Added golangci-lint configuration for better diagnostics
    • Created gui/.golangci.yml with line-number output format
    • Enabled print-issued-lines and sort-results
    • Replaced deprecated github-actions format
    • Will now show exact file:line for SA1006 errors

CI/CD

  • Updated GitHub Actions workflow with max-issues flags
  • Better error visibility for debugging lint issues

[0.1.13] - 2026-03-18

Fixed

  • Linting errors - Fixed remaining fmt.Fprintf SA1006 warnings
    • gui/main.go:105: fmt.Fprintf → fmt.Fprint (crash message)
    • gui/main.go:163: fmt.Fprintf → fmt.Fprint (startup failure message)
    • Functions without format verbs should use print-style

CI/CD

  • GitLab CI alignment - Synchronized with GitHub Actions
    • Updated golangci-lint from v1.55 to v1.64
    • Changed allow_failure from true to false (lint errors now block)
    • Added verbose output and line numbers
    • Both pipelines now enforce same quality standards

[0.1.12] - 2026-03-18

Fixed

  • CI/CD workflow improvements
    • Added GOWORK=off to golangci-lint step to prevent workspace-wide linting
    • Fixed hardcoded v0.4.0 in release notes (now uses dynamic version from tag)
    • Added verbose output and line numbers for better error reporting
    • Workflow now extracts changelog content automatically

Documentation

  • Updated README to focus on Nimbus Backup with RDEM Systems branding
  • Properly credited original project (tizbac/proxmoxbackupclient_go)
  • Removed detailed CLI documentation from fork
  • Cleaner structure for Windows GUI users

[0.1.11] - 2026-03-18

Fixed

  • Final Printf linting issues - Fixed remaining SA1006 warnings in machinebackup
    • machinebackup/windows.go:452: log.Printf → log.Print
    • machinebackup/windows.go:462: log.Printf → log.Print
    • Workspace-wide linting now fully clean

Code Quality

  • Zero linting warnings across all workspace modules
  • 100% golangci-lint compliance (gui + workspace modules)

[0.1.10] - 2026-03-18

Fixed

  • Final linting issue - Fixed last SA1006 staticcheck warning
    • snapshot/nop_snapshot.go: log.Printf → log.Print
    • All 3 Printf formatting issues now resolved
    • 100% golangci-lint compliance

Code Quality

  • Zero linting warnings
  • All staticcheck issues resolved
  • Production-grade code quality

[0.1.9] - 2026-03-18

Fixed

  • Linting issues - Fixed staticcheck SA1006 warnings
    • Changed Printf to Print for non-format strings
    • pbscommon/pbsapi.go: Printf → Print
    • snapshot/win_snapshot.go: Printf → Print
    • Cleaner code following Go best practices

Code Quality

  • All golangci-lint checks passing
  • Improved code formatting standards

[0.1.8] - 2026-03-18

Security

  • gosec G703 suppression - Added justified nosec annotation
    • Path validated with security.ValidatePath() before use
    • Static analysis limitation: can't detect runtime validation
    • Clear documentation of security measures taken
    • Zero unaddressed security issues

Documentation

  • Improved security annotation comments for audit trail

[0.1.7] - 2026-03-18

Security

  • Path traversal prevention - Fixed gosec G703 high severity
    • Added ValidatePath() check before log directory creation
    • Validates paths from environment variables (APPDATA/HOME)
    • Fallback to safe directory if validation fails
    • All gosec security checks now passing

CI/CD

  • GitHub Actions security job fully operational
  • Zero high/medium security issues

[0.1.6] - 2026-03-18

Fixed

  • GitHub Actions workflow - Automated dependency management
    • Added go mod tidy step before tests and linting
    • Automatic generation of go.sum in CI/CD
    • No more "updates to go.mod needed" errors
    • Consistent with GitLab CI behavior

CI/CD

  • Both pipelines now fully autonomous (no manual go mod tidy required)
  • Clean separation of concerns in workflow steps

[0.1.5] - 2026-03-18

Fixed

  • Go version consistency - Fixed remaining Go 1.24.4 references
    • directorybackup/go.mod: 1.24.4 → 1.22
    • machinebackup/go.mod: 1.24.4 → 1.22
    • nbd/go.mod: 1.24.4 → 1.22
    • All workspace modules now use Go 1.22 consistently

CI/CD

  • GitHub Actions and GitLab CI fully operational
  • No more "go version mismatch" errors
  • All builds pass successfully

[0.1.4] - 2026-03-18

Fixed

  • Module resolution - Fixed Go module imports for CI/CD
    • Created go.mod files for all pkg modules (logger, retry, security)
    • Simplified module names (pkg/retry → retry, pkg/security → security)
    • Fixed test file imports to use local module names
    • Fixed go.work Go version from 1.24.4 to 1.22
    • All modules now follow consistent pattern with replace directives

Technical

  • GitHub Actions and GitLab CI now pass successfully
  • go mod tidy works correctly with local pkg modules
  • No more "module not found" errors in CI

[0.1.2] - 2026-03-18

Added

  • Phase 2 Tests - Comprehensive test coverage
    • Chunking tests (pbscommon/chunking_test.go) - 15+ test cases including:
      • Deterministic chunking verification
      • Min/max boundary testing
      • Content-aware chunking
      • Incremental scanning
      • Average size validation
      • Edge cases (empty, small data, patterns)
      • Performance benchmarks
    • Snapshot tests (snapshot/snapshot_test.go) - Windows VSS testing:
      • Snapshot structure validation
      • Path handling for VSS
      • Callback pattern testing
      • Admin privilege detection
      • Symlink management

Security

  • Phase 3 Security - Hardened security throughout
    • Input validation integrated in all entry points:
      • SaveConfig() validates all fields before saving
      • StartBackup() validates BackupID and paths
      • TestConnection() validates credentials format
    • Credential sanitization in all log statements:
      • SanitizeSecret() for passwords/tokens
      • SanitizeURL() removes embedded credentials
      • SanitizeForLog() masks sensitive IDs
    • Comprehensive validation functions:
      • URL validation (HTTPS enforcement)
      • AuthID validation (user@realm!token format)
      • Datastore validation (alphanumeric)
      • BackupID validation (path traversal prevention)
      • Path validation (null byte detection)
      • Certificate fingerprint validation (SHA256 format)

[0.1.1] - 2026-03-18

Fixed

  • GitHub Actions CI/CD - Fixed go.work compatibility issues
    • Added gui module to go.work workspace
    • Set GOWORK: off environment variable in all workflow jobs
    • Fixed test and lint jobs to run in correct directories
    • Added missing frontend dependency installation steps

Improved

  • Network resilience - Added retry logic with exponential backoff
    • Chunk uploads retry up to 5 times with jitter
    • Chunk assignment retries with 5-minute timeout
    • Index finalization retries with backoff
    • Manifest upload retries with configurable delays
    • Context-aware cancellation for all retries
  • Error messages - More detailed error context after retry exhaustion

[0.1.0] - 2026-03-18 (First Public Release)

Refactoring (Phase 1 - Completed)

  • Comprehensive error handling throughout codebase
    • PXAR callbacks now return and propagate errors
    • HandleData() and Eof() with complete error checking
    • Replaced all panic() calls with graceful error handling
    • All errors wrapped with context using fmt.Errorf
  • Structured logging package (pkg/logger)
    • JSON-formatted logs with slog
    • Multiple log levels (Debug, Info, Warn, Error)
    • Comprehensive test coverage
  • Retry logic with exponential backoff (pkg/retry)
    • Configurable retry attempts and delays
    • Jitter support to prevent thundering herd
    • Context-aware cancellation
    • Comprehensive test coverage
  • Security package (pkg/security)
    • Input validation (URL, BackupID, Datastore, AuthID, Fingerprint, Path)
    • Credential sanitization for safe logging
    • Constant-time string comparison for secrets
    • Path traversal prevention

Planned

  • Client-side encryption - PBS supports encryption, add key management in config
    • Generate/import encryption keys
    • Store key securely in config (warn user to backup key!)
    • Encrypt chunks before upload to PBS
    • Key recovery mechanism
  • Code signing for Windows binaries (Authenticode certificate)
  • Auto-update system - Check for latest version and prompt for updates
  • System tray icon and background service
  • Automatic scheduling (daily, weekly, custom cron)
  • Windows service installation
  • Notification system (Windows toast)
  • Machine backup (full disk with PhysicalDrive - requires code signing)

[0.1.0] - 2026-03-18

Added

  • Initial Wails v2 GUI with React frontend
  • PBS server configuration interface
  • Directory backup mode with multi-folder support (one per line)
  • Real-time backup progress with accurate percentage
  • Background directory size calculation for precise ETA
  • Professional progress display (speed, elapsed time, ETA)
  • Granular progress updates (every 10 MB)
  • VSS (Volume Shadow Copy) support with admin privilege detection
  • Snapshot listing and restore functionality
  • PBS connection test with real authentication
  • Automatic hostname detection for backup-id
  • Debug logging to %APPDATA%\NimbusBackup\debug.log
  • Crash reporting system
  • RDEM Systems branding with custom icon

Technical

  • Inline backup implementation (no external binaries)
  • PXAR archive format support
  • Chunk deduplication with SHA256
  • Dynamic index creation (DIDX)
  • HTTP/2 protocol for PBS communication
  • Cross-platform build support (Windows primary)

Known Issues

  • Machine backup disabled due to Windows Defender false positive (PhysicalDrive syscalls)
  • Requires code signing certificate for full disk backup feature

Version Numbering

  • Major.Minor.Patch (Semantic Versioning)
  • Major: Breaking changes
  • Minor: New features, backwards compatible
  • Patch: Bug fixes, small improvements

Links