refactor(build-one): delegate ABI classification to bincraft #136
Loading…
Reference in a new issue
No description provided.
Delete branch "t3code/github-app-rate-limits"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Motivation
The weekly rebuild hit GitHub's per-user REST rate limit (HTTP 403 "API rate limit exceeded for user ID ..."). The root cause and the shared fix live in bincraft (rpkgs/bincraft#74): version resolution now comes from CRAN metadata instead of the GitHub tags API, and ABI classification is cached.
This PR wires the consumer side.
Changes
local/build-one.R:classify()no longer clonesgithub.com/cranand callsbincraft::needs_per_minor_recompile()itself. It now delegates to the newly exportedbincraft::classify_r_minor_sensitive(), passing the metadata-DB parameters so the verdict is fetched from the CRAN source tarball (no GitHub) and cached in theabi_classificationtable. Repeated runs and new-OS full rebuilds reuse the cached verdict.Behaviour change
Dependency
classify_r_minor_sensitive()). Merge and release that first; this branch only takes effect once CI installs the updated bincraft.