Skip to content

Conversation

carpentries-bot
Copy link

🤖 This is an automated build

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

# NEW OR REMOVED PACKAGES -------------------------------
- class       [required by classInt, e1071]
- KernSmooth  [required by classInt]
- MASS        [required by ggplot2]
- mgcv        [required by ggplot2]
- class        [7.3-23 -> *]
- KernSmooth   [2.23-26 -> *]
- MASS         [7.3-65 -> *]
- Matrix       [1.7-3 -> *]
- mgcv         [1.9-1 -> *]
- nlme         [3.1-168 -> *]
- R            [4.5.0 -> 4.5.1]

# CRAN -----------------------------------------------------------------------
- evaluate     [1.0.3 -> 1.0.4]
- reshape      [repo: RSPM -> CRAN; ver: 0.8.9 -> 0.8.10]
- tibble       [repo: RSPM -> CRAN; ver: 3.2.1 -> 3.3.0]
- utf8         [1.2.5 -> 1.2.6]
- class        [* -> 7.3-23]
- KernSmooth   [* -> 2.23-26]
- MASS         [* -> 7.3-65]
- Matrix       [* -> 1.7-3]
- mgcv         [* -> 1.9-1]
- nlme         [* -> 3.1-168]

# RSPM -----------------------------------------------------------------------
- fansi        [1.0.6 -> *]

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

Copy link

github-actions bot commented Jul 1, 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/datacarpentry/r-raster-vector-geospatial/compare/md-outputs..md-outputs-PR-481

The following changes were observed in the rendered markdown documents:

 config.yaml (gone)                                 |   92 -
 ...integration-rendered-compare-data-extents-1.png |  Bin 35228 -> 35259 bytes
 ...tion-rendered-repeat-compare-data-extents-1.png |  Bin 35228 -> 35259 bytes
 md5sum.txt                                         |   50 +-
 renv.lock (gone)                                   | 2746 --------------------
 5 files changed, 25 insertions(+), 2863 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-07-01 00:38:13 +0000

github-actions bot pushed a commit that referenced this pull request Jul 1, 2025
@jonjab jonjab merged commit 0707e19 into main Jul 11, 2025
3 checks passed
@jonjab jonjab deleted the update/packages branch July 11, 2025 16:28
github-actions bot pushed a commit that referenced this pull request Jul 11, 2025
Auto-generated via `{sandpaper}`
Source  : 0707e19
Branch  : main
Author  : Jon Jablonski <jonjab@ucsb.edu>
Time    : 2025-07-11 16:28:35 +0000
Message : Merge pull request #481 from datacarpentry/update/packages

Update 11 packages
github-actions bot pushed a commit that referenced this pull request Jul 11, 2025
Auto-generated via `{sandpaper}`
Source  : 734453b
Branch  : md-outputs
Author  : GitHub Actions <actions@github.com>
Time    : 2025-07-11 16:34:55 +0000
Message : markdown source builds

Auto-generated via `{sandpaper}`
Source  : 0707e19
Branch  : main
Author  : Jon Jablonski <jonjab@ucsb.edu>
Time    : 2025-07-11 16:28:35 +0000
Message : Merge pull request #481 from datacarpentry/update/packages

Update 11 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