Skip to content

ci: migrate the remaining workflows to baseline v2.0.0 callers - #47

Merged
seanthimons merged 6 commits into
mainfrom
ci/migrate-to-baseline-v2
Nov 13, 2026
Merged

seanthimons merged 6 commits into
mainfrom
ci/migrate-to-baseline-v2

Conversation

@seanthimons

Copy link
Copy Markdown
Owner

Finishes the move to seanthimons/baseline: every workflow in this repo is now a thin caller pinned to baseline v2.0.0 (0a6e332d70f7a15520c62870221b35ef040ef933). Also closes two stale beans.

Fixes #16, fixes #17, fixes #18, fixes #19, fixes #21, fixes #22.

Every change

  • .github/workflows/gitleaks.yaml, commit-lint.yaml, lint-workflows.yaml: repinned from v1.5.0 to v2.0.0. The gitleaks calling job now grants contents: read and pull-requests: read (v2.0.0's breaking change). Cron minute 53 kept.
  • .github/workflows/r-cmd-check.yaml: baseline caller, quarto: true; keeps the NEWS.md / **/*.md paths-ignore; drops the .planning/** ignore (no such directory).
  • .github/workflows/pkgdown.yaml: baseline caller, quarto: true.
  • .github/workflows/release.yaml: baseline release-r-package caller, quarto: true (also implied by the default autonewsmd notes).
  • .github/workflows/build-package.yaml: baseline caller, quarto: true.
  • .github/zizmor.yml: deleted; its time-boxed artipacked ignores were for the old pkgdown.yaml and release.yaml.
  • .beans/boosterpak-mt5x-*.md, .beans/boosterpak-83qe-*.md: marked completed with the evidence (the hook already uses try(); no failing tests).

Behavior changes

R CMD check:

  • Warnings now fail the check (error-on: warning, the callee default).
  • Runs on PRs to any branch (old: PRs to main only); the github-actions[bot] skip is gone (release commits still carry [skip ci]).
  • 60-minute job timeout, serial testthat on Windows, R_PROFILE_USER=/dev/null, renv autoloader off. Same 3-OS matrix on R release.

pkgdown:

Release:

  • Dispatch inputs are now version-type (patch, minor, major, dev) and dry-run; the old version_type input and its none option are gone, so there is no re-release without a bump.
  • main and the tag are pushed with git push --atomic; a failed publish can be rerun on its own (fixes ci: make release.yaml push atomic and recoverable after partial failure #16). RELEASE_PAT is used only by the push and publish steps; build and check run with a read-only token and no persisted credentials (fixes ci: scope the release push token to the push step in release.yaml #17).
  • One chore: release vX.Y.Z [skip ci] commit replaces the separate bump and NEWS commits. NEWS.md headings change to the callee's format. devtools::document() no longer runs at release time. R CMD check runs on the built tarball. Releases must start from main unless dry-run is set. The release attaches the tarball and SHA256SUMS.

Build package: same artifact name and retention; 20-minute timeout.

All workflows: newer pinned actions inside the callees (checkout v7.0.1 and others), owned and bumped in baseline.

Check names

Checks now report as caller / callee, for example R CMD check / ubuntu-latest (release) and pkgdown / .... The protect-default-branch ruleset has no required status checks, so nothing blocks on the renamed checks.

Settings changes at merge (owner approved doing them through the API)

  1. Pages source from "Deploy from a branch (gh-pages)" to "GitHub Actions", right before merging, so the merge's pkgdown run deploys.
  2. Add a v* tag rule to the github-pages environment's deployment policy, so release-triggered pkgdown runs can deploy.
  3. Delete the gh-pages branch after the first successful Actions deploy.

Other issues

Validation

Local actionlint clean and offline zizmor 1.32.0 reports no findings (with .github/zizmor.yml removed). Full testthat suite passes. Each commit had a separate diff audit. The CI on this PR runs the new callers; the pkgdown deploy, a release dry run, and the Pages switch can only be exercised after merge.

@seanthimons
seanthimons merged commit dd08e29 into main Nov 13, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment