Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 11 packages #171

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update 11 packages #171

wants to merge 1 commit into from

Conversation

Bisaloo
Copy link
Member

@Bisaloo Bisaloo commented Dec 3, 2024

🤖 This is an automated build

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

# NEW OR REMOVED PACKAGES -------------------------------
- MASS      [required by arm, ciTools, ggplot2, and 2 others]
- Matrix    [required by arm, lme4]
- mgcv      [required by ggplot2]
- survival  [required by ciTools]
- MASS             [7.3-61 -> *]
- Matrix           [1.7-1 -> *]
- mgcv             [1.9-1 -> *]
- survival         [3.7-0 -> *]
- epiparameter     [epiverse-trace/epiparameter@main: d3ab3284 -> 1c94e679]
- epiparameterDB   [* -> epiverse-trace/epiparameterDB]
- R                [4.4.1 -> 4.4.2]

# CRAN -----------------------------------------------------------------------
- curl          [6.0.0 -> 6.0.1]
- fontawesome   [repo: RSPM -> CRAN; ver: 0.5.2 -> 0.5.3]
- grates        [1.2.2 -> 1.3.0]
- incidence2    [2.5.0 -> 2.6.0]
- RSQLite       [2.3.7 -> 2.3.8]
- ympes         [1.6.0 -> 1.7.0]
- MASS          [* -> 7.3-61]
- Matrix        [* -> 1.7-1]
- mgcv          [* -> 1.9-1]
- survival      [* -> 3.7-0]

⏱️ 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 Dec 3, 2024

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-early/compare/md-outputs..md-outputs-PR-171

The following changes were observed in the rendered markdown documents:

 clean-data.md         |    14 +-
 config.yaml (gone)    |    83 -
 data/cleaned_data.csv | 29998 ++++++++++++++++++++++++------------------------
 md5sum.txt            |    32 +-
 renv.lock (gone)      |  2238 ----
 5 files changed, 15022 insertions(+), 17343 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 2024-12-03 00:52:12 +0000

github-actions bot pushed a commit that referenced this pull request Dec 3, 2024
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.

1 participant