Repository navigation
Conversation
Collaborator
Author
|
the checks are expected to be red here. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Both workflows in
.github/workflows/were last touched in 2021, and since thenevery action they pin has been superseded and one of the runner labels they
target no longer exists. Neither workflow can currently complete a single job.
R-CMD-check.yml:ubuntu-20.04no longer exists. GitHub announced the deprecation of theimage in December 2024 and retired it on 15 April 2025. A job aimed at a
retired label never gets a runner: it waits out the 24-hour job timeout and
is then cancelled — that is what the
1d 0hruns in this repository are.ubuntu-latestreplaces it.macos-latestis arm64 since late 2024.r-lib/actions/setup-r@v1predates Apple Silicon runners and has no arm64 R build to fetch.
setup-r@v2handles the architecture natively.actions/checkout@v2,actions/cache@v2,r-lib/actions/setup-r@v1andsetup-pandoc@v1areforced onto Node 20 by GitHub now and are no longer maintained. Bumped to
checkout@v4andr-lib/actions@v2.setup-r-dependencies@v2and
check-r-package@v2replace the manualremotes::dev_package_deps()caching, the
system_requirements("ubuntu", "20.04")call (which installsfocal packages on a jammy/noble runner) and the direct
rcmdcheckcall, andthey install system libraries through pak.
permissions: read-all, aworkflow_dispatchtrigger so the workflowcan be started by hand on any branch, and
devel/oldrel-1on Ubuntu —what
usethis::use_github_action("check-standard")generates today.test-coverage.yaml:actions/cache@v2in this file is a hard failure, not a warning — the cacheservice for v1/v2 was shut down in February 2025, so the run dies before the
first step with "This request has been automatically failed because it uses a
deprecated version of
actions/cache: v2". Same fix: ther-lib/actions@v2stack, which caches through pak.
codecov/codecov-action@v4needs aCODECOV_TOKENsecret.fail_ci_if_erroris set to
falseso a missing token produces a warning rather than failingthe job after the package has already been tested; flip it back once the
secret exists.
ubuntu-latest(it was running Windows only) and added the testthatlog dump and failure-artifact upload from the r-lib example.
No package code is touched —
.github/workflows/only.Verification
All five jobs green in the author's fork, where Actions are not blocked:
https://github.com/vsimko/corrplot/actions/runs/40426424436
Note for the maintainer: at the time of writing, jobs in
taiyun/corrplotfailwith
The job was not started because your account is locked due to a billing issue. That affects unrelated PRs in this repository too (#288), so the runs onthis PR may show that same failure rather than a result of the patch — the
billing issue needs resolving on the account before any workflow here can run.