Release archive
3.2.53

CRYPTO-GITHUB-ACTIVITY-FALLBACK (Repo Push Signal)

Release v3.2.53 focuses on CRYPTO-GITHUB-ACTIVITY-FALLBACK (Repo Push Signal).

FixedInternal
CRYPTO-GITHUB-ACTIVITY-FALLBACK (Repo Push Signal)

Release digest

Fixed

  • CRYPTO-GITHUB-ACTIVITY-FALLBACK (Repo Push Signal) — Crypto project pages now surface a truthful Repo active fallback when GitHub organization repositories expose recent pushed_at activity but the commit API is degraded or rate-limited, preventing live-token projects such as LayerZero from staying stuck in a pending development-metrics state.

Internal

  • Added regression coverage for degraded GitHub commit API handling, metadata repair acceptance of repo-push fallback activity, and crypto page copy that distinguishes repo activity from missing active-developer counts.
  • Verified targeted crypto harvester, service, and frontend runtime-contract tests locally.
  • Verified the dashboard production build locally after the crypto UI copy change.
  • Updated release notes for the production-visible crypto GitHub activity fallback. No knowledge-base update is required because this is an authenticated dashboard reliability correction and does not introduce public setup, API, or legal guidance.

Technical notes