From ccf45753abd30ea715d5af01579a2de653bb92c9 Mon Sep 17 00:00:00 2001 From: Julia Silge Date: Mon, 7 Oct 2024 10:52:02 -0600 Subject: [PATCH] Release candidate 1.4.0 (#846) * Update URLs * Rev dep checks * Update NEWS * Redocument * Increment version number to 1.4.0 --- DESCRIPTION | 2 +- NEWS.md | 2 +- R/legacy_azure.R | 1 - cran-comments.md | 2 +- man/legacy_azure.Rd | 1 - man/pins-package.Rd | 4 ++-- revdep/README.md | 23 +++++++++++++++++++++++ revdep/cran.md | 2 +- vignettes/pins.Rmd | 2 +- 9 files changed, 30 insertions(+), 9 deletions(-) diff --git a/DESCRIPTION b/DESCRIPTION index cb22e6e8e..a5f65f476 100644 --- a/DESCRIPTION +++ b/DESCRIPTION @@ -1,7 +1,7 @@ Type: Package Package: pins Title: Pin, Discover, and Share Resources -Version: 1.3.0.9000 +Version: 1.4.0 Authors@R: c( person("Julia", "Silge", , "julia.silge@posit.co", role = c("cre", "aut"), comment = c(ORCID = "0000-0002-3671-836X")), diff --git a/NEWS.md b/NEWS.md index fb7c4bb97..a62b84555 100644 --- a/NEWS.md +++ b/NEWS.md @@ -1,4 +1,4 @@ -# pins (development version, to be released as 1.4.0) +# pins 1.4.0 ## Lifecycle changes diff --git a/R/legacy_azure.R b/R/legacy_azure.R index 92ec21055..52a6b97c9 100644 --- a/R/legacy_azure.R +++ b/R/legacy_azure.R @@ -5,7 +5,6 @@ #' #' To use Microsoft Azure Storage as a board, you'll need an Azure Storage #' account, an Azure Storage container, and an Azure Storage key. -#' You can sign-up and create those at [portal.azure.com](https://portal.azure.com). #' @inheritParams legacy_datatxt #' @param container The name of the Azure Storage container. #' @param account The name of the Azure Storage account. diff --git a/cran-comments.md b/cran-comments.md index ce2e82b77..c19edf42d 100644 --- a/cran-comments.md +++ b/cran-comments.md @@ -1,6 +1,6 @@ ## revdepcheck results -We checked 4 reverse dependencies, comparing R CMD check results across CRAN and dev versions of this package. +We checked 7 reverse dependencies, comparing R CMD check results across CRAN and dev versions of this package. * We saw 0 new problems * We failed to check 0 packages diff --git a/man/legacy_azure.Rd b/man/legacy_azure.Rd index 813c0dae9..3131fecf1 100644 --- a/man/legacy_azure.Rd +++ b/man/legacy_azure.Rd @@ -54,7 +54,6 @@ board object.} To use Microsoft Azure Storage as a board, you'll need an Azure Storage account, an Azure Storage container, and an Azure Storage key. -You can sign-up and create those at \href{https://portal.azure.com}{portal.azure.com}. } \examples{ \dontrun{ diff --git a/man/pins-package.Rd b/man/pins-package.Rd index a97359f7e..132aa58f5 100644 --- a/man/pins-package.Rd +++ b/man/pins-package.Rd @@ -4,11 +4,11 @@ \name{pins-package} \alias{pins} \alias{pins-package} -\title{pins: Pin, Discover and Share Resources} +\title{pins: Pin, Discover, and Share Resources} \description{ \if{html}{\figure{logo.png}{options: style='float: right' alt='logo' width='120'}} -Publish data sets, models, and other R objects, making it easy to share them across projects and with your colleagues. You can pin objects to a variety of "boards", including local folders (to share on a networked drive or with 'DropBox'), 'RStudio' connect, Amazon S3, and more. +Publish data sets, models, and other R objects, making it easy to share them across projects and with your colleagues. You can pin objects to a variety of "boards", including local folders (to share on a networked drive or with 'DropBox'), 'Posit Connect', 'AWS S3', and more. } \seealso{ Useful links: diff --git a/revdep/README.md b/revdep/README.md index 52e12c714..7559a6f6a 100644 --- a/revdep/README.md +++ b/revdep/README.md @@ -1,2 +1,25 @@ +# Platform + +|field |value | +|:--------|:------------------------------------------| +|version |R version 4.4.0 (2024-04-24) | +|os |macOS 15.0 | +|system |aarch64, darwin20 | +|ui |X11 | +|language |(EN) | +|collate |en_US.UTF-8 | +|ctype |en_US.UTF-8 | +|tz |America/Denver | +|date |2024-10-06 | +|pandoc |3.2.1 @ /opt/homebrew/bin/ (via rmarkdown) | + +# Dependencies + +|package |old |new |Δ | +|:-------|:-----|:----------|:--| +|pins |1.3.0 |1.3.0.9000 |* | +|askpass |NA |1.2.1 |* | +|sys |NA |3.4.3 |* | + # Revdeps diff --git a/revdep/cran.md b/revdep/cran.md index ab1853cee..7bdf5de9d 100644 --- a/revdep/cran.md +++ b/revdep/cran.md @@ -1,6 +1,6 @@ ## revdepcheck results -We checked 4 reverse dependencies, comparing R CMD check results across CRAN and dev versions of this package. +We checked 7 reverse dependencies, comparing R CMD check results across CRAN and dev versions of this package. * We saw 0 new problems * We failed to check 0 packages diff --git a/vignettes/pins.Rmd b/vignettes/pins.Rmd index 8bd48cdcc..bcc11d8a1 100644 --- a/vignettes/pins.Rmd +++ b/vignettes/pins.Rmd @@ -76,7 +76,7 @@ But you can choose another option depending on your goals: - `type = "parquet"` uses `nanoparquet::write_parquet()` to create a Parquet file. [Parquet](https://parquet.apache.org/) is a modern, language-independent, column-oriented file format for efficient data storage and retrieval. Parquet is an excellent choice for storing tabular data but requires the [nanoparquet](https://nanoparquet.r-lib.org/) package. - `type = "arrow"` uses `arrow::write_feather()` to create an Arrow/Feather file. - `type = "json"` uses `jsonlite::write_json()` to create a JSON file. Pretty much every programming language can read json files, but they only work well for nested lists. -- `type = "qs"` uses `qs::qsave()` to create a binary R data file, like `writeRDS()`. This format achieves faster read/write speeds than RDS, and compresses data more efficiently, making it a good choice for larger objects. Read more on the [qs package](https://github.com/traversc/qs). +- `type = "qs"` uses `qs::qsave()` to create a binary R data file, like `writeRDS()`. This format achieves faster read/write speeds than RDS, and compresses data more efficiently, making it a good choice for larger objects. Read more on the [qs package](https://github.com/qsbase/qs). Note that when the data lives elsewhere, pins takes care of downloading and caching so that it's only re-downloaded when needed. That said, most boards transmit pins over HTTP, and this is going to be slow and possibly unreliable for very large pins.