fix(ci): do not gate the targeted repair on the source classifier #205
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/repair-must-not-gate-on-source-classifier"
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?
Why
The repair workflow ran
build-one.R --sensitive-only. That flag skips any version the source classifier does not call r-minor-sensitive — and it missesRcpp.So the repair skipped
Rcppon every slot, leaving its 4.5-built flat binary as the only copy:Every R 4.4 client on those slots then failed at
dyn.load(). A real install check across 8 slots x 3 minors x 3 repository forms found 44 such failures,Rcpp,MatrixandRJSONIOamong them.What changed
Drops
--sensitive-only.Since bincraft v5.3.0 the destination is decided by the built binary's symbols in
upload_single_binary(), so building unconditionally is safe and correct: a package that needs a per-minor slot lands there, one that does not lands in the flat slot. Skipping before the build is exactly what removed that decision from the path.crow lintpasses.Companion
bincraft #129 is the other half: the index build could not compensate either, because it only considered dropping records whose package was flagged risky, and
Rcppis not — even though the backfill had recorded that object as unable to load under 4.4.