Skip to content

[CI][R] Ship a Windows libarrow binary built with Rtools45 alongside the Rtools40 one #55624

Open

Description

@thisisnic

Describe the enhancement requested

GH-55398 moved the per-PR windows-cpp job in .github/workflows/r.yml to Rtools45, but the Windows libarrow binary that users download is still built only with Rtools40, by the r-binary-packages crossbow task (dev/tasks/r/github.packages.yml).

The plan is to ship both: a zip built with Rtools45 for current R versions, and the Rtools40 zip for older ones.

To do:

  • Add an Rtools45 windows-cpp job to the crossbow task, next to the Rtools40 one. ci/scripts/r_windows_build.sh already supports both via RTOOLS_VERSION.
  • Give the two zips distinct names; both are currently r-libarrow-windows-x86_64.
  • Make the R package pick the right zip for the R version being used. r/configure.win already handles both zip layouts once one is unpacked.
  • Test the R package on Windows against both zips.

Component(s)

Continuous Integration, Packaging, R

Activity

  1. self-assigned this
    on Nov 15, 2026
  2. changed the title [-][R][Packaging] Ship a Windows libarrow binary built with Rtools45 alongside the Rtools40 one[/-] [+][CI][R][Packaging] Ship a Windows libarrow binary built with Rtools45 alongside the Rtools40 one[/+] on Nov 15, 2026
  3. changed the title [-][CI][R][Packaging] Ship a Windows libarrow binary built with Rtools45 alongside the Rtools40 one[/-] [+][CI][R] Ship a Windows libarrow binary built with Rtools45 alongside the Rtools40 one[/+] on Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions