Release archive
3.2.54

CRYPTO-GITHUB-PUBLIC-READ-FALLBACK (Rejected Token Recovery)

Release v3.2.54 focuses on CRYPTO-GITHUB-PUBLIC-READ-FALLBACK (Rejected Token Recovery).

FixedInternal
CRYPTO-GITHUB-PUBLIC-READ-FALLBACK (Rejected Token Recovery)

Release digest

Fixed

  • CRYPTO-GITHUB-PUBLIC-READ-FALLBACK (Rejected Token Recovery) — GitHub harvesting now retries public GitHub reads without authorization when the configured token is rejected with 401 or 403, so a stale production token cannot block public repository activity signals for projects such as LayerZero.

Internal

  • Added regression coverage for rejected-token org reads falling back to the unauthenticated public GitHub API while preserving truthful repo-push activity fallback behavior.
  • Verified targeted crypto harvester, metadata-repair, and frontend runtime-contract tests locally.
  • Updated release notes for the production GitHub public-read recovery. No knowledge-base update is required because this is an internal harvester reliability correction and does not introduce public setup, API, or legal guidance.

Technical notes