-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: [R] Verify CRAN release-19.0.1 #45597
Conversation
Thanks for opening a pull request! If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project. Then could you also rename the pull request title in the following format?
or
See also: |
@github-actions crossbow submit --group r |
Revision: fed7eb7 Submitted crossbow builds: ursacomputing/crossbow @ actions-b7b0e0b19b |
I'll cherry-pick #45524 ( |
…with R lintr (#45524) ### Rationale for this change The linting jobs are failing due to the new version of `lintr` not installing `cyclocomp` anymore. We use `cyclocomp` but this is not part of the default linters of `lintr` anymore. We should install it individually. ### What changes are included in this PR? Install `cyclocomp` as part of setting up the linting environment for R on our linting job. Pin old version of `lintr` for R Windows job as it otherwise fails with a lot of new linter issues. ### Are these changes tested? Yes via CI. ### Are there any user-facing changes? No * GitHub Issue: #45521 Authored-by: Raúl Cumplido <raulcumplido@gmail.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Looks good now, closing and moving forward with CRAN prep. |
Caution
Do not merge this PR.
This PR is being used to prepare for the CRAN submission for 19.0.1.
See packaging checklist: #45581.