Skip to content

Conversation

@carpentries-bot
Copy link

🤖 This is an automated build

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

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

# CRAN -----------------------------------------------------------------------
- data.table   [1.17.0 -> 1.17.4]
- 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]
- MASS         [* -> 7.3-65]
- Matrix       [* -> 1.7-3]
- mgcv         [* -> 1.9-1]
- nlme         [* -> 3.1-168]

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

# https://carpentries.r-universe.dev -----------------------------------------
- curl         [repo: CRAN -> https://carpentries.r-universe.dev; ver: 6.2.2 -> 6.2.3; ref: * -> v6.2.3; sha: * -> c23c0fba]

⏱️ 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 Jun 3, 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/LibraryCarpentry/lc-r/compare/md-outputs..md-outputs-PR-121

The following changes were observed in the rendered markdown documents:

 config.yaml (gone)                                 |   85 -
 ...t-rendered-boxplot-exercise-subcollection-1.png |  Bin 46887 -> 45713 bytes
 ...a-viz-ggplot-rendered-boxplot-with-points-1.png |  Bin 42071 -> 42288 bytes
 ...data-viz-ggplot-rendered-unnamed-chunk-14-1.png |  Bin 37437 -> 38170 bytes
 fig/04-data-viz-ggplot-rendered-violin-plot-1.png  |  Bin 37272 -> 37343 bytes
 md5sum.txt                                         |   30 +-
 renv.lock (gone)                                   | 4045 --------------------
 7 files changed, 15 insertions(+), 4145 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-06-03 00:31:18 +0000

github-actions bot pushed a commit that referenced this pull request Jun 3, 2025
@jt14den jt14den merged commit 0c275a4 into main Jun 3, 2025
3 checks passed
@jt14den jt14den deleted the update/packages branch June 3, 2025 00:38
github-actions bot pushed a commit that referenced this pull request Jun 3, 2025
Auto-generated via `{sandpaper}`
Source  : 0c275a4
Branch  : main
Author  : Tim Dennis <[email protected]>
Time    : 2025-06-03 00:38:32 +0000
Message : Merge pull request #121 from LibraryCarpentry/update/packages

Update 10 packages
github-actions bot pushed a commit that referenced this pull request Jun 3, 2025
Auto-generated via `{sandpaper}`
Source  : 9fdaeda
Branch  : md-outputs
Author  : GitHub Actions <[email protected]>
Time    : 2025-06-03 00:40:21 +0000
Message : markdown source builds

Auto-generated via `{sandpaper}`
Source  : 0c275a4
Branch  : main
Author  : Tim Dennis <[email protected]>
Time    : 2025-06-03 00:38:32 +0000
Message : Merge pull request #121 from LibraryCarpentry/update/packages

Update 10 packages
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