Update 14 packages

[epiverse-trace-bot]

🤖 This is an automated build

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

# NEW OR REMOVED PACKAGES -------------------------------
- MASS      [required by fitdistrplus, ggplot2]
- Matrix    [required by igraph]
- mgcv      [required by ggplot2]
- survival  [required by fitdistrplus]
- lattice    [0.22-7 -> *]
- MASS       [7.3-65 -> *]
- Matrix     [1.7-3 -> *]
- mgcv       [1.9-1 -> *]
- nlme       [3.1-168 -> *]
- survival   [3.8-3 -> *]

# CRAN -----------------------------------------------------------------------
- curl           [6.2.2 -> 6.2.3]
- data.table     [1.17.0 -> 1.17.4]
- fastymd        [repo: RSPM -> CRAN; ver: 0.1.2 -> 0.1.3]
- generics       [repo: RSPM -> CRAN; ver: 0.1.3 -> 0.1.4]
- haven          [repo: RSPM -> CRAN; ver: 2.5.4 -> 2.5.5]
- openssl        [2.3.2 -> 2.3.3]
- pkgbuild       [1.4.7 -> 1.4.8]
- RcppParallel   [repo: RSPM -> CRAN; ver: 5.1.7 -> 5.1.10]
- MASS           [* -> 7.3-65]
- Matrix         [* -> 1.7-3]
- mgcv           [* -> 1.9-1]
- nlme           [* -> 3.1-168]
- survival       [* -> 3.8-3]

# RSPM -----------------------------------------------------------------------
- lattice        [* -> 0.22-7]

⏱️ 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

• Auto-generated by create-pull-request on 2025-06-03

[github-actions]

NOTE: This Pull Request (#192) was previously merged

[avallecam]

Hi @Bisaloo, possibly this RcppParallel thing is one of the blockers I would like to work on to keep it as smooth as possible.

Is there a way to say to sandpaper or renv: do not update RcppParallel? Or something like: always update it from RSPM?

Am I correct in saying that neither writing pak::pak("RcppParallel") at episodes/install.R nor writing sandpaper::pin_version("RcppParallel@5.1.7") would stabilise this? Both are mentioned in the same documentation page. The first worked for epidemics at tutorials repo, but not sure if able to stabilise and fix the version too.

[avallecam]

Alternatively, I can just add the TO-DO step to the CONTRIBUTING file to keep the same package Version and Repository, each time this error keeps happening.