v0.6.3

Bug Fix

v0.6.2

Bug Fix

v0.6.1

Bug Fixes

v0.6.0

Bug fix and New features and UI.

v0.5.1

📢 Important Note on Star History Deprecation

• Stargazers Endpoint Restrictions: Due to recent GitHub API policy adjustments restricting stargazer detailed lists to repository owners and collaborators, the fetch_star_history function and local server endpoints have been updated.
• Graceful Restriction Handling: Attempting to query star history for repositories you do not own or collaborate on will now raise a clean, specific StargazersRestrictedError (returning a 403 Forbidden response in the web API and displaying a descriptive restriction message in the CLI) instead of raising generic/internal server errors.

🛠️ Improvements & Bug Fixes

• Layout Enhancements: Adjusted dashboard grid spacing for the customizer panels, layout columns, and metrics grid to prevent overlapping labels or text clipping.
• Security & Cleanups: Improved internal error mapping on REST API routes and cleaned up CLI subcommand arguments.

v0.5.0

v0.5.0 — GitHub API Restriction Fix & Direct Exports

Key Highlights

• GitHub API Restriction Fix: Gracefully handles GitHub's June 30, 2026 /stargazers restriction with specific error classes, access restrictions, and descriptive fallback SVGs.
• Interactive Multi-Repo Star Chart: Upgrades Star History in Token/Cloud modes to a cumulative line chart showing multiple repositories in distinct colors with toggle checkbox pills.
• Direct Downloads with Loading State: Adds quick PNG/SVG export buttons to charts (hidden for badges) that display a spinner animation and text feedback during compilation.

v0.4.8

Star generator bug fix

v0.4.7 - Bug Fix

Bug Fix

v0.4.6 — Bugfix release

Fixes:

• Legacy Title Case columns (Total Views, Unique Visitors, etc.) are properly mapped — no more silent zero data
• Python 3.9 compatibility restored via from future import annotations
• Star-history endpoint rejects malformed Authorization headers instead of leaking the server PAT
• Private-repo redaction now consistent between JSON and CSV export paths
• Bad repo names in fetch --repo-name no longer kill the entire fetch
• Malformed dates in sync data are logged instead of silently dropped
• numpy added as explicit dependency

v0.4.5

Gitlytics v0.4.5 — Release Notes

This release resolves a critical cross-month data routing bug in the database-appending command.

Bug Fixes

• Fixed Cross-Month Data Placement:
  Previously, file names for monthly database logs (traffic_YYYY-MM.csv) were determined based on the execution date of the sync script instead of the actual data timestamps.
  • The Fix: Data is now automatically grouped by its actual date. For example, late June data retrieved during a July 1st sync will correctly append to traffic_YYYY-06.csv instead of writing to traffic_YYYY-07.csv.
• Zero Empty Files: Empty/header-only log files will no longer be created for upcoming months until actual daily records exist for that month.