Chore/modernize ci - #169
Merged
Merged
Conversation
PR 5 — Modernize GitHub Actions + ggplot2 release/devel matrix (START HERE) .github/workflows/check-standard.yaml and pkgdown.yaml use actions/checkout@v3, actions/cache@v3, and actions/upload-artifact@main (a floating tag) and skip Linux. Bump to current pinned action versions; replace @main. Add an Ubuntu runner. Add a ggplot2 release + devel matrix (the r-lib/actions/check-r-package template supports this) so ggplot2 breakage is caught before it reaches a user mid-render. check-standard.yaml — full rewrite onto the modern r-lib/actions v2 pattern: Replaced the hand-rolled remotes + manual cache + rcmdcheck steps with setup-r-dependencies + check-r-package (handles caching, system deps, and result upload internally). Killed the risky actions/upload-artifact@main floating tag entirely (the modern action manages artifacts itself). Added an OS matrix: macOS, Windows, and Ubuntu (previously commented out). Added backward + forward compat: oldrel-1 (guards your R >= 3.5 floor) and a ggplot2-devel canary — an Ubuntu job that installs github::tidyverse/ggplot2 and is marked continue-on-error: true, so it reports upcoming ggplot2 breakage (the theme_set() and #164 class of problems) without blocking merges. Set error-on: '"error"' to match the repo's prior behavior — so existing size-deprecation warnings don't turn everything red before PR 6 lands. pkgdown.yaml — minimal safe bump: actions/checkout@v3 → v4 (both spots) and actions/cache@v3 → v4. The private CMAP-fonts checkout, the font-install step, and both deploy_to_branch steps are untouched. One judgment call to flag The ggplot2-devel job is deliberately non-blocking. That's the right default for a canary, but it means its signal only shows if someone looks at the checks list — it won't fail a PR. If you'd rather it be load-bearing once #164 and the theme work are fixed, flip allow_failure off in a later PR. I noted the reasoning in a comment in the file.
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
2 participants
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.
From AI - What PR 5 does
check-standard.yaml — full rewrite onto the modern r-lib/actions v2 pattern:
Replaced the hand-rolled remotes + manual cache + rcmdcheck steps with setup-r-dependencies + check-r-package (handles caching, system deps, and result upload internally).
Killed the risky actions/upload-artifact@main floating tag entirely (the modern action manages artifacts itself).
Added an OS matrix: macOS, Windows, and Ubuntu (previously commented out).
Added backward + forward compat: oldrel-1 (guards your R >= 3.5 floor) and a ggplot2-devel canary — an Ubuntu job that installs github::tidyverse/ggplot2 and is marked continue-on-error: true, so it reports upcoming ggplot2 breakage (the theme_set() and #164 class of problems) without blocking merges.
Set error-on: '"error"' to match the repo's prior behavior — so existing size-deprecation warnings don't turn everything red before PR 6 lands.
pkgdown.yaml — minimal safe bump: actions/checkout@v3 → v4 (both spots) and actions/cache@v3 → v4. The private CMAP-fonts checkout, the font-install step, and both deploy_to_branch steps are untouched.
One judgment call to flag
The ggplot2-devel job is deliberately non-blocking. That's the right default for a canary, but it means its signal only shows if someone looks at the checks list — it won't fail a PR. If you'd rather it be load-bearing once #164 and the theme work are fixed, flip allow_failure off in a later PR. I noted the reasoning in a comment in the file.