Repository navigation
ci: migrate the remaining workflows to baseline v2.0.0 callers - #47
Merged
Merged
Conversation
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.
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 grantscontents: readandpull-requests: read(v2.0.0's breaking change). Cron minute53kept..github/workflows/r-cmd-check.yaml: baseline caller,quarto: true; keeps theNEWS.md/**/*.mdpaths-ignore; drops the.planning/**ignore (no such directory)..github/workflows/pkgdown.yaml: baseline caller,quarto: true..github/workflows/release.yaml: baselinerelease-r-packagecaller,quarto: true(also implied by the default autonewsmd notes)..github/workflows/build-package.yaml: baseline caller,quarto: true..github/zizmor.yml: deleted; its time-boxedartipackedignores were for the oldpkgdown.yamlandrelease.yaml..beans/boosterpak-mt5x-*.md,.beans/boosterpak-83qe-*.md: marked completed with the evidence (the hook already usestry(); no failing tests).Behavior changes
R CMD check:
error-on: warning, the callee default).mainonly); thegithub-actions[bot]skip is gone (release commits still carry[skip ci]).R_PROFILE_USER=/dev/null, renv autoloader off. Same 3-OS matrix on R release.pkgdown:
upload-pages-artifact+deploy-pages) instead of pushing togh-pages; each deploy replaces the whole site.RELEASE_PATstart the pkgdown run (fixes ci: pkgdown release trigger never fires because releases use GITHUB_TOKEN #18), given the Pages environment allowsv*tags (see below).Release:
version-type(patch,minor,major,dev) anddry-run; the oldversion_typeinput and itsnoneoption are gone, so there is no re-release without a bump.mainand the tag are pushed withgit 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_PATis 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).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 frommainunlessdry-runis 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 exampleR CMD check / ubuntu-latest (release)andpkgdown / .... Theprotect-default-branchruleset has no required status checks, so nothing blocks on the renamed checks.Settings changes at merge (owner approved doing them through the API)
v*tag rule to thegithub-pagesenvironment's deployment policy, so release-triggered pkgdown runs can deploy.gh-pagesbranch after the first successful Actions deploy.Other issues
[A-Za-z0-9_]+, no bot skip); closing separately.boosters/attach.R); closing separately.Validation
Local actionlint clean and offline zizmor 1.32.0 reports no findings (with
.github/zizmor.ymlremoved). 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.