feat: Release 0.6.0

.Rbuildignore

@@ -12,3 +12,5 @@
 ^\.github$
 ^cran-comments\.md$
 ^CRAN-SUBMISSION$
+
+^jarl\.toml$

DESCRIPTION

@@ -1,7 +1,7 @@
 Package: flir
 Type: Package
 Title: Find and Fix Lints in R Code
-Version: 0.5.0.9000
+Version: 0.6.0
 Authors@R:
     c(person(given = "Etienne",
              family = "Bacher",

NEWS.md

@@ -1,4 +1,4 @@
-# flir (development version)
+# flir 0.6.0
 
 ## New features
 

R/utils.R

@@ -58,7 +58,7 @@ get_tests_from_lintr <- function(name) {
     "_linter.R"
   )
   dest <- paste0("tests/testthat/test-", name, ".R")
-  utils::download.file(url, destfile = dest)
+  utils::download.file(url, destfile = dest, mode = "wb")
   if (rlang::is_interactive()) {
     utils::file.edit(dest)
   }

cran-comments.md

@@ -1,14 +0,0 @@
-This is the first CRAN release (3rd try).
-
-Thank you for the comments, I have updated the functions that write to the user
-file system so that the argument `path` has to be specified. Note that in tests
-only (which don't write to the working directory), a missing `path` means that
-`"."` is used by default.
-
-While I understand the willingness to minimize automatic changes to the user's
-file system, I must say there's quite a discrepancy in how this policy is
-applied. Many CRAN packages (including some of my own) directly write to the user
-file system without asking for user confirmation such as `altdoc`, `devtools`,
-`pkgdown`, `rextendr`, `Rcpp`, `roxygen2`, etc. Therefore, from the package
-developer's point of view, it's hard to understand why this usage is accepted
-for some packages but not others.

inst/WORDLIST

@@ -4,14 +4,14 @@ Bundock
 CMD
 Github
 Jagan
+Jarl
 Linters
 Mikael
+ORCID
 RStudio
-YAML
 ast
 astgrepr
 coercions
-config
 fleer
 formatter
 grepl
@@ -20,8 +20,9 @@ lapply
 len
 linter
 linters
+lintr
 nlevels
-repo
+nzchar
 sourceMarkers
 stopifnot
 unstaged