ci: build last four minor R versions instead of only the latest #6
Loading…
Reference in a new issue
No description provided.
Delete branch "t3code/2a207854"
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?
Summary
The crow build pipeline previously built only the single latest stable R version (from the brew formula).
It now builds the latest patch release of each of the last four minor R versions and uploads any that are missing from S3, so older supported minors stay available rather than only the newest stable.
versions.json(the same source upstream'stest/get_r_versions.pyuses) via jq — keep onlyx.y.zreleases, take the latest patch per minor, then the top four minors (e.g.4.6.0, 4.5.3, 4.4.3, 4.3.3).awk fix
The existence check used an awk regex (
$0 ~ ver), so the unescaped dots in a version made4.4.3spuriously match4.3.3(the substring4/4.3satisfies the pattern).Harmless with a single version, but across four adjacent versions it would wrongly skip builds.
Switched to literal substring matching via awk
index($0, ver).