Custom publication titles supported via .gitpulse.json
Developers can now set custom publication titles and move per-project settings into a committed .gitpulse.json file instead of managing them through environment variables.
Gitpulse now reads project configuration from a .gitpulse.json file at the repo root. Publication title and subtitle — previously auto-generated — can now be overridden by adding these values to the config file. Four operational settings (bootstrapDays, concurrency, releasesCap, and includePrereleases) have also migrated from environment variables to this file, keeping project-specific preferences versioned alongside the code.
The change simplifies deployment: instead of configuring the same settings across every CI environment or hosting platform, teams commit them once. Validation uses Zod with clear error messages that name the offending field, so misconfiguration is easy to diagnose.
The config is optional. When absent, Gitpulse falls back to the existing auto-generated defaults.
This affects the CLI's analyze phase and the site's rendering layer, which now reads the custom title and subtitle from the same data file.