Skip to content

Conversation

@epiverse-trace-bot
Copy link

@epiverse-trace-bot epiverse-trace-bot commented Sep 2, 2025

🤖 This is an automated build

This will update 68 packages in your lesson with the following versions:

# NEW OR REMOVED PACKAGES -------------------------------
- MASS      [required by arm, ciTools, fitdistrplus, and 2 others]
- nlme      [required by arm, lme4, mgcv]
- survival  [required by ciTools, fitdistrplus]
- MASS       [7.3-65 -> *]
- nlme       [3.1-168 -> *]
- survival   [3.8-3 -> *]
- R          [4.5.1 -> 4.5.2]

# CRAN -----------------------------------------------------------------------
- BH              [repo: RSPM -> CRAN; ver: 1.87.0-1 -> 1.90.0-1]
- boot            [repo: RSPM -> CRAN; ver: 1.3-31 -> 1.3-32]
- broom           [1.0.8 -> 1.0.11]
- checkmate       [2.3.2 -> 2.3.3]
- cleanepi        [1.1.0 -> 1.1.2]
- colorspace      [2.1-1 -> 2.1-2]
- crosstalk       [1.2.1 -> 1.2.2]
- curl            [6.4.0 -> 7.0.0]
- data.table      [1.17.6 -> 1.18.0]
- dbplyr          [2.5.0 -> 2.5.1]
- digest          [0.6.37 -> 0.6.39]
- dtplyr          [1.3.1 -> 1.3.2]
- evaluate        [1.0.4 -> 1.0.5]
- fastymd         [0.1.3 -> 0.1.4]
- forcats         [1.0.0 -> 1.0.1]
- futile.logger   [repo: RSPM -> CRAN; ver: 1.4.3 -> 1.4.9]
- gargle          [1.5.2 -> 1.6.0]
- ggplot2         [3.5.2 -> 4.0.1]
- googledrive     [2.1.1 -> 2.1.2]
- googlesheets4   [1.1.1 -> 1.1.2]
- grates          [1.5.0 -> 1.7.1]
- hms             [1.1.3 -> 1.1.4]
- htmltools       [0.5.8.1 -> 0.5.9]
- igraph          [2.1.4 -> 2.2.1]
- isoband         [0.2.7 -> 0.3.0]
- knitr           [1.50 -> 1.51]
- lme4            [1.1-37 -> 1.1-38]
- loo             [2.8.0 -> 2.9.0]
- magrittr        [2.0.3 -> 2.0.4]
- Matrix          [1.7-3 -> 1.7-4]
- openssl         [2.3.3 -> 2.3.4]
- pak             [0.9.0 -> 0.9.2]
- patchwork       [1.3.1 -> 1.3.2]
- pillar          [1.10.2 -> 1.11.1]
- pkgload         [1.4.0 -> 1.4.1]
- purrr           [1.0.4 -> 1.2.0]
- QuickJSR        [1.8.0 -> 1.8.1]
- ragg            [1.4.0 -> 1.5.0]
- rbibutils       [2.3 -> 2.4]
- Rcpp            [1.0.14 -> 1.1.0]
- RcppParallel    [5.1.10 -> 5.1.11-1]
- readr           [2.1.5 -> 2.1.6]
- reformulas      [0.4.1 -> 0.4.3]
- rmarkdown       [2.29 -> 2.30]
- rprojroot       [2.0.4 -> 2.1.1]
- rstantools      [2.4.0 -> 2.5.0]
- runner          [0.4.4 -> 0.4.5]
- rvest           [1.0.4 -> 1.0.5]
- selectr         [repo: RSPM -> CRAN; ver: 0.4-2 -> 0.5-1]
- simulist        [0.5.0 -> 0.6.0]
- stringr         [1.5.1 -> 1.6.0]
- systemfonts     [1.2.3 -> 1.3.1]
- testthat        [3.2.3 -> 3.3.1]
- textshaping     [1.0.1 -> 1.0.4]
- tidyr           [1.3.1 -> 1.3.2]
- tinytex         [0.57 -> 0.58]
- visNetwork      [repo: RSPM -> CRAN; ver: 2.1.2 -> 2.1.4]
- vroom           [1.6.5 -> 1.6.7]
- waldo           [0.6.1 -> 0.6.2]
- xfun            [0.52 -> 0.55]
- xml2            [1.3.8 -> 1.5.1]
- yaml            [repo: RSPM -> CRAN; ver: 2.3.10 -> 2.3.12]
- MASS            [* -> 7.3-65]
- nlme            [* -> 3.1-168]
- S7              [* -> 0.2.1]
- survival        [* -> 3.8-3]

# RSPM -----------------------------------------------------------------------
- mgcv            [1.9-3 -> *]

# https://packagemanager.posit.co/cran/__linux__/jammy/latest ----------------
- ring            [repo: CRAN -> https://packagemanager.posit.co/cran/__linux__/jammy/latest; ver: 1.0.6 -> 1.0.8]

⏱️ In a few minutes, a comment will appear that will show you how the output has changed based on these updates.

If you want to inspect these changes locally, you can use the following code to check out a new branch:

git fetch origin update/packages
git checkout update/packages

@github-actions
Copy link

github-actions bot commented Sep 2, 2025

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

  • 🎯 correct output
  • 🖼️ correct figures
  • ❓ new warnings
  • ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/epiverse-trace/tutorials/compare/md-outputs..md-outputs-PR-215

The following changes were observed in the rendered markdown documents:

 config.yaml (gone)                                 |   87 -
 delays-distribution.md                             |    4 +-
 delays-introduction.md                             |   24 +-
 ...ys-introduction-rendered-unnamed-chunk-12-1.png |  Bin 4380 -> 4348 bytes
 ...ys-introduction-rendered-unnamed-chunk-15-1.png |  Bin 5142 -> 5138 bytes
 ...ays-introduction-rendered-unnamed-chunk-5-1.png |  Bin 7433 -> 6022 bytes
 install.R                                          |    2 +
 md5sum.txt                                         |   24 +-
 renv.lock (gone)                                   | 7352 --------------------
 9 files changed, 28 insertions(+), 7465 deletions(-)
What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2026-01-08 16:47:37 +0000

@epiverse-trace-bot epiverse-trace-bot changed the title Update 26 packages Update 68 packages Jan 6, 2026
github-actions bot pushed a commit that referenced this pull request Jan 6, 2026
github-actions bot pushed a commit that referenced this pull request Jan 6, 2026
github-actions bot pushed a commit that referenced this pull request Jan 8, 2026
@avallecam avallecam merged commit 65cda48 into main Jan 8, 2026
6 checks passed
@avallecam avallecam deleted the update/packages branch January 8, 2026 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants