From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: R cran updates
Date: Sat, 24 Jun 2023 04:05:55 +0200 [thread overview]
Message-ID: <20230624020555.N83IX3-az8HCSjDX6kqiAxhnuBBwxVIce1I21MmrtJU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42704@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]
There's a closed pull request on the void-packages repository
R cran updates
https://github.com/void-linux/void-packages/pull/42704
Description:
* R-cran-zoo: update to 1.8r11
* R-cran-utf8: update to 1.2.3
* R-cran-svglite: update to 2.1.1
* R-cran-stringr: update to 1.5.0
* R-cran-stringi: update to 1.7.8
* R-cran-purrr: update to 1.0.1
* R-cran-plyr: update to 1.8.8
* R-cran-nloptr: update to 2.0.3, adopt
* R-cran-testthat: update to 3.1.6
* New package: R-cran-waldo-0.4.0
* New package: R-cran-rematch2-2.1.2
* New package: R-cran-diffobj-0.3.5
* R-cran-pkgload: update to 1.3.2
* R-cran-rstudioapi: update to 0.14
* R-cran-pkgbuild: update to 1.4.0
* New package: R-cran-fs-1.6.1
* New package: R-cran-jsonlite-1.8.4
* New package: R-cran-brio-1.1.3
* R-cran-lubridate: update to 1.9.2
* New package: R-cran-timechange-0.2.0
* R-cran-ggplot2: update to 3.4.1
* R-cran-scales: update to 1.2.1
* R-cran-isoband: update to 0.2.7
* R-cran-gtable: update to 0.3.1
* R-cran-evaluate: update to 0.20
* R-cran-dplyr: update to 1.1.0
* R-cran-tibble: update to 3.2.0
* R-cran-vctrs: update to 0.5.2
* R-cran-fansi: update to 1.0.4
* R-cran-digest: update to 0.6.31
* R-cran-desc: update to 1.4.2
* R-cran-rprojroot: update to 2.0.3
* R-cran-data.table: update to 1.14.8
* R-cran-colorspace: update to 2.1.r0
* R-cran-cli: update to 3.6.0
* R-cran-callr: update to 3.7.3
* R-cran-processx: update to 3.8.0
* R-cran-ps: update to 1.7.2
* R-cran-backports: update to 1.4.1
* R-cran-RInside: update to 0.2.18
* R-cran-Rcpp: update to 1.0.10
* R-cran-RColorBrewer: update to 1.8r11
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
next prev parent reply other threads:[~2023-06-24 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 17:37 [PR PATCH] " hervyqa
2023-03-11 18:02 ` [PR PATCH] [Updated] " hervyqa
2023-06-10 2:00 ` github-actions
2023-06-24 2:05 ` github-actions [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-13 0:46 [PR PATCH] " CameronNemo
2022-08-02 2:14 ` [PR PATCH] [Closed]: " github-actions
2022-08-17 2:15 ` github-actions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230624020555.N83IX3-az8HCSjDX6kqiAxhnuBBwxVIce1I21MmrtJU@z \
--to=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).