Skip to content

Update 18 packages#114

Merged
avallecam merged 1 commit intomainfrom
update/packages
Oct 30, 2025
Merged

Update 18 packages#114
avallecam merged 1 commit intomainfrom
update/packages

Conversation

@epiverse-trace-bot
Copy link
Copy Markdown

🤖 This is an automated build

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

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

# CRAN -----------------------------------------------------------------------
- broom         [1.0.8 -> 1.0.9]
- checkmate     [repo: RSPM -> CRAN; ver: 2.3.2 -> 2.3.3]
- curl          [6.4.0 -> 7.0.0]
- data.table    [1.17.6 -> 1.17.8]
- evaluate      [1.0.4 -> 1.0.5]
- pillar        [1.10.2 -> 1.11.0]
- purrr         [1.0.4 -> 1.1.0]
- Rcpp          [1.0.14 -> 1.1.0]
- renv          [1.1.4 -> 1.1.5]
- rvest         [repo: RSPM -> CRAN; ver: 1.0.4 -> 1.0.5]
- textshaping   [1.0.1 -> 1.0.2]
- V8            [6.0.4 -> 7.0.0]
- xfun          [0.52 -> 0.53]
- xml2          [1.3.8 -> 1.4.0]
- MASS          [* -> 7.3-65]
- Matrix        [* -> 1.7-3]
- nlme          [* -> 3.1-168]

# 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

@github-actions
Copy link
Copy Markdown

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-late/compare/md-outputs..md-outputs-PR-114

The following changes were observed in the rendered markdown documents:

 config.yaml (gone)                               |   86 -
 fig/model-choices-rendered-unnamed-chunk-4-1.png |  Bin 8995 -> 9161 bytes
 md5sum.txt                                       |   36 +-
 renv.lock (gone)                                 | 5116 ----------------------
 4 files changed, 18 insertions(+), 5220 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 2025-10-07 01:06:24 +0000

github-actions Bot pushed a commit that referenced this pull request Sep 2, 2025
github-actions Bot pushed a commit that referenced this pull request Oct 7, 2025
@avallecam avallecam merged commit faf7b1d into main Oct 30, 2025
6 checks passed
@avallecam avallecam deleted the update/packages branch October 30, 2025 10:58
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.

3 participants