A notification about a change to check.ci.ocaml.org, the opam health-check service that periodically builds every package in opam-repository across several compiler versions.
Viewing individual build log pages (/log/...) now requires signing in with GitHub. The first time you open a log, you’ll be prompted to complete a one-time GitHub authorisation screen, then land back on the log you requested. Sessions last 30 days.
Everything else is still public, including the results dashboard, package filters, diffs between runs, and the JSON API (/api/v2/latest/packages), all of which work anonymously, exactly as before.
The log pages have been under constant, heavy crawling from distributed scraper farms with spoofed browser user-agents. Every log fetch incurs an extraction from the compressed run archives, and at scraper volumes, this has repeatedly degraded or taken the site offline for actual users. After exploring cheaper storage/serving options, we concluded that a lightweight login is the pragmatic fix: it adds negligible friction for humans and a complete block for bots.
The OAuth app (owned by the ocurrent org) requests no scopes — we never see your email, repos, or anything beyond your public GitHub username, and nothing is stored server-side (sessions are stateless signed cookies).
If you have tooling that fetches log pages programmatically and this breaks your workflow, or you encounter any issues with the login flow, please reply here or open an issue on ocurrent/opam-health-check.