What's Changed
Follow-up to v3.15.4 — relaxes the dashboard config gate so users with tokens but no username don't get locked out.
Fixed
-
Dashboard rendered all zeros for users whose config had empty
usernamefields (#271). TheuseConfigStatushook requiredgithubConfig.usernameandgiteaConfig.usernameto be non-empty before letting the dashboard fetch data. In practice neither is required at runtime:- The GitHub token is self-authenticating via
listForAuthenticatedUser— no username needed. - The Gitea username isn't used under
single-orgorflat-usermirror strategies.
Users who configured via env vars without setting
GITHUB_USERNAME/GITEA_USERNAME(the form'srequiredattribute is only client-side and the save endpoint doesn't enforce it either) ended up with empty strings in those fields. Mirroring kept running fine because tokens alone are sufficient — but the dashboard refused to fetch and rendered zeros.The gate now only requires what's actually needed at runtime: the GitHub token, and the Gitea URL + token. The
githubOwnerfield is still exported for consumers that want to display an owner; only the gate is relaxed. - The GitHub token is self-authenticating via
Compatibility
No schema changes, no migrations. Pure frontend hook change.
Verification
All 231 unit tests pass. bun run build succeeds.
Full Changelog: v3.15.4...v3.15.5