Skip to content

fix: compatibility with primarycensored >= 1.4.0 #1687

fix: compatibility with primarycensored >= 1.4.0

fix: compatibility with primarycensored >= 1.4.0 #1687

Triggered via pull request April 8, 2026 14:16
Status Cancelled
Total duration 45m 39s
Artifacts 3

R-CMD-check.yaml

on: pull_request
Matrix: R-CMD-check
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 4 warnings
macOS-latest (release)
Process completed with exit code 1.
macOS-latest (release)
R CMD check found ERRORs
ubuntu-latest (release)
Process completed with exit code 1.
ubuntu-latest (release)
R CMD check found ERRORs
ubuntu-latest (oldrel-1)
Process completed with exit code 1.
ubuntu-latest (oldrel-1)
R CMD check found ERRORs
R-CMD-check
Canceling since a higher priority waiting request for R-CMD-check-fix/primarycensored-L-param exists
windows-latest (release)
Canceling since a higher priority waiting request for R-CMD-check-fix/primarycensored-L-param exists
windows-latest (release)
The operation was canceled.
macOS-latest (release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, r-lib/actions/setup-pandoc@v2, r-lib/actions/setup-r@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ubuntu-latest (release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, r-lib/actions/setup-pandoc@v2, r-lib/actions/setup-r@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ubuntu-latest (oldrel-1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, r-lib/actions/setup-pandoc@v2, r-lib/actions/setup-r@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
windows-latest (release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, r-lib/actions/setup-pandoc@v2, r-lib/actions/setup-r@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
Linux-X64-roldrel-1-2-results
4.05 MB
sha256:1cc5fca41d376b4f7e1248e6c01f43fa26b195788c2313accb2333fce52a531d
Linux-X64-rrelease-1-results
4.04 MB
sha256:88e53e372b09cb1ec2645ba54240d238f25bc94bbdf838909388fa67abd5df56
macOS-ARM64-rrelease-3-results
4.49 MB
sha256:8001cae596993649946fe98794eccb3e3bc3038bf4b3317781f7c7d5eb7e22cc