Skip to content

sync-ci: CRAN checks key off CRAN membership, independent of tier#7

Merged
joethorley merged 1 commit into
mainfrom
f-ci-cran-detect
Jun 21, 2026
Merged

sync-ci: CRAN checks key off CRAN membership, independent of tier#7
joethorley merged 1 commit into
mainfrom
f-ci-cran-detect

Conversation

@joethorley

Copy link
Copy Markdown
Member

Follow-up to #6. CRAN-only checks (check-no-suggests + vendored rhub.yaml) were gated on tier == cran, so a registry-pinned tier suppressed them for CRAN packages. Now CRAN membership is detected for every package and drives the cran flag independent of tier.

  • mcmcderive (registry important, on CRAN) now gets the important matrix and check-no-suggests + rhub.
  • No change for plain CRAN packages (still tier=cran, cran=true) or non-CRAN important packages (cran=false).
  • Dry-run output now shows a cran= column so it is visible which packages get the CRAN checks.

Unit-tested the classification for important-on-CRAN, plain-CRAN, and important-not-CRAN cases.

🤖 Generated with Claude Code

A registry-pinned tier (e.g. important) previously suppressed the
CRAN-only checks even for packages on CRAN, because the cran flag was
tier==cran. Detect CRAN membership for every package and gate
check-no-suggests + vendored rhub.yaml on that, independent of tier
(e.g. mcmcderive: tier=important, cran=true). Surface cran in the dry-run
output so it is visible which packages get the CRAN checks.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@joethorley joethorley merged commit 748e5cc into main Jun 21, 2026
1 check failed
@joethorley joethorley deleted the f-ci-cran-detect branch June 21, 2026 01:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant