Release quarto 1.4

[cderv]

Prepare for release:

• git pull
• Check current CRAN check results
• Polish NEWS
• urlchecker::url_check()
• devtools::check(remote = TRUE, manual = TRUE)
• devtools::check_win_devel()
• revdepcheck::revdep_check(num_workers = 4) / revdepcheck::cloud_check()
• Update cran-comments.md
• git push
• Draft blog post

Submit to CRAN:

• usethis::use_version('minor')
• devtools::submit_cran()
• Approve email

Wait for CRAN...

• Accepted 🎉
• Finish & publish blog post
• Add link to blog post in pkgdown news menu
• usethis::use_github_release()
• usethis::use_dev_version(push = TRUE)
• Tweet

[cderv]

Problem with CRAN release. Automated check on DEBIAN fails due to vignette not built I think.

* checking package vignettes ... NOTE
Package has ‘vignettes’ subdirectory but apparently no vignettes.
Perhaps the ‘VignetteBuilder’ information is missing from the
DESCRIPTION file?

Probably quarto CLI is not installed on this machine.

Need to find how to release in this context.

[cderv]

I can reproduce the issue using R-hub docker image debian-gcc-devel (https://cloud.r-project.org/web/packages/rhub/vignettes/local-debugging.html) so that is good first step

[cderv]

It seems those ones are better: https://r-hub.github.io/containers/

[cderv]

Can't reproduce on docker image... It only happens on CRAN environment. So release is still block but I'll try get more more information on how to get this working.

[cderv]

This is solved and on CRAN now after some back and forth by email and r-package-devel mailing.

It seems there was a bug in R CMD check in specific situation that this package with new vignette engine triggered