v1.1.1

Author: amoeba

DESCRIPTION

@@ -1,5 +1,5 @@
 Package: dataspice
-Version: 1.1.0
+Version: 1.1.1
 Title: Create Lightweight Schema.org Descriptions of Data
 Description: The goal of 'dataspice' is to make it easier for researchers to
   create basic, lightweight, and concise metadata files for their datasets.

NEWS.md

@@ -1,5 +1,9 @@
 # NEWS
 
+## dataspice 1.1.1
+
+This release updates dataspice's tests to be compatible with the upcoming stringr 1.6.0 release.
+
 ## dataspice 1.1.0
 
 This release is for the version of the package after going through [rOpenSci Onboarding](https://github.com/ropensci/software-review/issues/426).

README.Rmd

@@ -72,7 +72,7 @@ The template files are:
 
 ### Fill in templates
 
-The user needs to fill in the details of the four template files. These csv files can be directly modified, or they can be edited using either the associated helper function and/or [Shiny](https://shiny.rstudio.com/) app.
+The user needs to fill in the details of the four template files. These csv files can be directly modified, or they can be edited using either the associated helper function and/or [Shiny](https://shiny.posit.co/) app.
 
 #### Helper functions
 
@@ -119,7 +119,7 @@ readr::read_csv(
 
 #### Shiny helper apps
 
-Each of the metadata templates can be edited interactively using a [Shiny](https://shiny.rstudio.com/) app:
+Each of the metadata templates can be edited interactively using a [Shiny](https://shiny.posit.co/) app:
 
 * `edit_attributes()` opens a Shiny app that can be used to edit `attributes.csv`. The Shiny app displays the current `attributes` table and lets the user fill in an informative description and units (e.g. meters, hectares, etc.) for each variable.
 * `edit_access()` opens an editable version of `access.csv`

README.md

@@ -3,7 +3,7 @@
 ![CRAN Version](https://www.r-pkg.org/badges/version/dataspice)
 ![CI](https://github.com/ropensci/dataspice/workflows/R-CMD-check/badge.svg)
 [![Codecov test
-coverage](https://codecov.io/gh/ropensci/dataspice/branch/main/graph/badge.svg)](https://codecov.io/gh/ropensci/dataspice?branch=main)
+coverage](https://codecov.io/gh/ropensci/dataspice/branch/main/graph/badge.svg)](https://app.codecov.io/gh/ropensci/dataspice?branch=main)
 [![](https://badges.ropensci.org/426_status.svg)](https://github.com/ropensci/software-review/issues/426)
 
 The goal of `dataspice` is to make it easier for researchers to create
@@ -80,7 +80,7 @@ The template files are:
 The user needs to fill in the details of the four template files. These
 csv files can be directly modified, or they can be edited using either
 the associated helper function and/or
-[Shiny](https://shiny.rstudio.com/) app.
+[Shiny](https://shiny.posit.co/) app.
 
 #### Helper functions
 
@@ -229,7 +229,7 @@ NA
 #### Shiny helper apps
 
 Each of the metadata templates can be edited interactively using a
-[Shiny](https://shiny.rstudio.com/) app:
+[Shiny](https://shiny.posit.co/) app:
 
 -   `edit_attributes()` opens a Shiny app that can be used to edit
     `attributes.csv`. The Shiny app displays the current `attributes`
@@ -336,17 +336,17 @@ record which is totally fine:
 
 ``` r
 library(EML)
-#> 
+#>
 #> Attaching package: 'EML'
 #> The following object is masked from 'package:magrittr':
-#> 
+#>
 #>     set_attributes
 
 eml_validate(eml_doc)
 #> [1] FALSE
 #> attr(,"errors")
-#> [1] "Element '{https://eml.ecoinformatics.org/eml-2.2.0}eml': The attribute 'packageId' is required but missing."                                  
-#> [2] "Element '{https://eml.ecoinformatics.org/eml-2.2.0}eml': The attribute 'system' is required but missing."                                     
+#> [1] "Element '{https://eml.ecoinformatics.org/eml-2.2.0}eml': The attribute 'packageId' is required but missing."
+#> [2] "Element '{https://eml.ecoinformatics.org/eml-2.2.0}eml': The attribute 'system' is required but missing."
 #> [3] "Element 'dataTable': Missing child element(s). Expected is one of ( physical, coverage, methods, additionalInfo, annotation, attributeList )."
 #> [4] "Element 'dataTable': Missing child element(s). Expected is one of ( physical, coverage, methods, additionalInfo, annotation, attributeList )."
 #> [5] "Element 'dataTable': Missing child element(s). Expected is one of ( physical, coverage, methods, additionalInfo, annotation, attributeList )."

codemeta.json

@@ -12,7 +12,7 @@
   "codeRepository": ["https://github.com/ropensci/dataspice"],
   "issueTracker": ["https://github.com/ropensci/dataspice/issues"],
   "license": ["https://spdx.org/licenses/MIT"],
-  "version": ["1.1.0"],
+  "version": ["1.1.1"],
   "programmingLanguage": {
     "@type": ["ComputerLanguage"],
     "name": ["R"],

cran-comments.md

@@ -1,15 +1,15 @@
 # cran-comments
 
-This is a minor release submission and is largely made of changes to documentation and tests.
+This is a patch release submission and primarily updates tests to be compliant with new dependency versions.
 
 ## Test environments
 
 On GitHub Actions:
 
-- windows (release)
+- Windows (release)
 - macOS (release)
-- ubuntu-20.04 (release)
-- ubuntu-20.04 (devel)
+- ubuntu-24.04 (release)
+- ubuntu-24.04 (devel)
 
 ## R CMD check
 

vignettes/overview.Rmd

@@ -27,7 +27,7 @@ To start the user will have one or more datafiles in a common directory. We curr
 Once these are created, you need to fill in each template file with the remaining metadata.
 Templates can be filled either:
 
-1. With the integrated [Shiny](https://shiny.rstudio.com/) applications (`edit_attributes()`, `edit_access()`, `edit_creators()`, `edit_biblio()`)
+1. With the integrated [Shiny](https://shiny.posit.co/) applications (`edit_attributes()`, `edit_access()`, `edit_creators()`, `edit_biblio()`)
 2. Manually (i.e., with a text or CSV/spreadsheet editor)
 
 For new and even advanced users, option (1) is probably easier and more friendly.