Skip to content

Add a release workflow running blockr.ci's release gate - #14

Merged
nbenn merged 1 commit into
mainfrom
13-release-gate
Sep 25, 2026
Merged

nbenn merged 1 commit into
mainfrom
13-release-gate

Conversation

@nbenn

@nbenn nbenn commented Sep 25, 2026

Copy link
Copy Markdown
Owner

Summary

  • Adds .github/workflows/release.yaml, named release, which calls blockr.ci's reusable release-gate.yaml on pull requests carrying the release label.
  • On such a PR the mechanical CRAN checks run on every push and report in one comment the gate rewrites each time; spelling, URLs and the --as-cran notes advise without failing.
  • Ordinary PRs show one skipped job, and nothing joins the required checks. A job skipped at the caller never creates the called workflow's contexts, so requiring one means moving that condition inside first.

Fixes #13

@nbenn nbenn added the release Release-prep PR: CRAN submission candidate label Sep 25, 2026
@github-actions

Copy link
Copy Markdown

Release gate — 19e0011

❌ A hard gate fails at this commit.

Hard gates

Check Result
Version has exactly three components ❌ version (0.0.0.9000) should have exactly three components
No dependency pinned to a development version ✅ 2 pinned, none a devel version
No Remotes field in DESCRIPTION ✅ no Remotes field
NEWS.md is not build-ignored, no stale inst/NEWS.Rd ➖ no NEWS.md
No placeholder vignette titles ➖ no vignettes/ directory

Rd \value sections

✅ Every documented function has a \value section.

README freshness

❌ The README did not render, so its freshness is unknown: ! in callr subprocess.
Caused by error in library(sqlr.sqlite):
! there is no package called 'sqlr.sqlite'

Soft checks

Reported on every push, never a gate.

Spelling

⚠️ 21 word(s) not in the dictionary or inst/WORDLIST.

  • behaviour -- README.md:155, README.Rmd:143
  • btree -- sqlr_constraint.Rd:61
  • catalogue -- sqlr_constraint.Rd:90, sqlr_reflect.Rd:25, sqlr_render_type.Rd:18, sqlr_schema.Rd:30, README.md:105, README.Rmd:96
  • catalogues -- sqlr_schema.Rd:6
  • CMD -- README.md:8, README.Rmd:19
  • DBIConnection -- sqlr_reflect.Rd:13, sqlr_register_dialect.Rd:13,18
  • dbplyr -- README.md:16, README.Rmd:26
  • DDL -- README.md:126, README.Rmd:115
  • Lifecycle -- README.md:10, README.Rmd:20
  • modelled -- sqlr_constraint.Rd:89, README.md:167, README.Rmd:154
  • onLoad -- sqlr_register_dialect.Rd:25
  • positionally -- sqlr_table.Rd:22
  • Postgres -- README.md:126, README.Rmd:115
  • recognise -- as_sqlr_type.Rd:17, sqlr_identity.Rd:41
  • renderable -- sqlr_constraint.Rd:95
  • schemas -- sqlr_diff.Rd:6, sqlr_schema.Rd:30, README.md:132,167,176, README.Rmd:120,154,162
  • Schemas -- sqlr_schema.Rd:6, sqlr-package.Rd:7, title:1
  • sql -- sqlr_constraint.Rd:82, sqlr_identity.Rd:33, sqlr_sql.Rd:13
  • unmodelled -- sqlr_type.Rd:118
  • untestable -- README.md:155, README.Rmd:143
  • varchar -- as_sqlr_type.Rd:17

URLs

✅ All URLs resolve.

R CMD check --no-manual --as-cran --run-donttest

⚠️ 1 finding(s) from the CRAN incoming checks.

Notes

checking CRAN incoming feasibility ... [3s/10s] NOTE
Maintainer: ‘Nicolas Bennett <r@nbenn.ch>’

New submission

Version contains large components (0.0.0.9000)

Reverse dependencies are checked by recheck in the release workflow, which runs on its own clock — read it in the checks for this commit.

Rewritten by release-gate on every push, so this always describes the head commit.

@nbenn nbenn removed the release Release-prep PR: CRAN submission candidate label Sep 25, 2026
The mechanical CRAN checks run on every push to a pull request
labelled release and report in one comment, so a release-prep branch
shows what CRAN will flag before the tarball is built from it.
@nbenn
nbenn marked this pull request as ready for review September 25, 2026 07:04
@nbenn
nbenn merged commit 64ef51c into main Sep 25, 2026
9 checks passed
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.

Run the CRAN release checks on pull requests labelled release

1 participant