GitBack v0.5.5

A logging overhaul. GitBack logs are now structured, actionable, and ready for production use — whether you're feeding them into a SIEM, automated analysis, or reviewing an incident manually.

What's New

🧾 Structured, Actionable Logging

Every log entry now explains what happened, when it happened, why it happened, and what to do next.

🔄 Daily Log Rotation

GitBack no longer writes to a single ever-growing log file.

Logs are now rotated daily using your local time:

gitback-2026-09-05-saturday.log

Retention is configurable:

[logging]
retention_days = 30   # Delete log files older than this many days
min_keep = 10          # Always retain at least the 10 most recent files

min_keep protects infrequent schedules. If GitBack only runs weekly or monthly, older logs won't all disappear during a single retention cleanup.

🤖 Machine-Parseable Log Entries

Every log entry now contains stable, machine-friendly fields, including:

• A stable event code
• Fixed severity
• The affected asset
• A fixed failure category where applicable

Failure categories such as auth_failure and corruption remain consistent across GitBack versions, making logs suitable for reliable SIEM rules, dashboards, and automated analysis without depending on fragile text matching.

🖥️ Machine and Account Context

Every log entry now identifies the machine and account that produced it.

This is particularly useful when GitBack runs across multiple servers or under different system accounts, making it immediately clear where an event originated.

⚙️ Complete Configuration Example

Run:

gitback config example

to see a fully documented example configuration containing every available setting, including defaults and notes about important edge cases.

Upgrade Notes

This release changes the on-disk log format.

Existing log files are left untouched, but newly generated logs use the new format.

Configuration Compatibility

No changes to config.toml are required.

The new [logging] settings have sensible defaults and are only needed when you want to customize retention behavior.

Full Changelog

Full Changelog: v0.5.4...v0.5.5