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: Wed, 17 Aug 2022 04:15:05 +0200 [thread overview]
Message-ID: <20220817021505.FdmboezG9sKOKwSYG3JhcLjqqn08LRQyiWIpZ6NvnQo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36119@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]
There's a closed pull request on the void-packages repository
R cran updates
https://github.com/void-linux/void-packages/pull/36119
Description:
- R-cran-R6: update to 2.5.1
- R-cran-cli: update to 3.2.0
- R-cran-colorspace: update to 2.0r3
- R-cran-cpp11: update to 0.4.2
- R-cran-crayon: update to 1.5.0
- R-cran-digest: update to 0.6.29
- R-cran-dplyr: update to 1.0.8
- R-cran-ellipsis: update to 0.3.2
- R-cran-fansi: update to 1.0.2
- R-cran-farver: update to 2.1.0
- R-cran-generics: update to 0.1.2
- R-cran-glue: update to 1.6.2
- R-cran-isoband: update to 0.2.5
- R-cran-labeling: update to 0.4.2
- R-cran-lifecycle: update to 1.0.1
- R-cran-magrittr: update to 2.0.2
- R-cran-pillar: update to 1.7.0
- R-cran-rlang: update to 1.0.2
- R-cran-svglite: update to 2.1.0
- R-cran-systemfonts: update to 1.0.4
- R-cran-tibble: update to 3.1.6
- R-cran-tidyselect: update to 1.1.2
- R-cran-utf8: update to 1.2.2
- R-cran-vctrs: update to 0.3.8
- R-cran-viridisLite: update to 0.4.0
- R-cran-withr: update to 2.5.0
@luhann
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
next prev parent reply other threads:[~2022-08-17 2:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 0:46 [PR PATCH] " CameronNemo
2022-03-13 1:38 ` luhann
2022-04-10 3:22 ` [PR PATCH] [Updated] " CameronNemo
2022-07-10 2:15 ` github-actions
2022-07-17 21:50 ` [PR PATCH] [Updated] " CameronNemo
2022-07-17 22:05 ` CameronNemo
2022-07-18 3:27 ` CameronNemo
2022-07-18 3:39 ` CameronNemo
2022-08-02 2:14 ` [PR PATCH] [Closed]: " github-actions
2022-08-02 19:59 ` [PR PATCH] [Updated] " CameronNemo
2022-08-17 2:15 ` github-actions [this message]
2023-03-11 17:37 [PR PATCH] " hervyqa
2023-06-24 2:05 ` [PR PATCH] [Closed]: " 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=20220817021505.FdmboezG9sKOKwSYG3JhcLjqqn08LRQyiWIpZ6NvnQo@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).