tidyverse 1.3.0

Photo by Juskteez Vu

Mara Averick

We’re thrilled to announce that tidyverse 1.3.0 is now on CRAN. The tidyverse is a set of packages that work in harmony because they share common data representations and API design. The tidyverse package is a “meta” package designed to make it easy to install and load core packages from the tidyverse in a single command. This is great for teaching and interactive use, but for package development purposes we recommend that authors import only the specific packages that they use. For a complete list of changes, please see the release notes.

You can install the latest version of tidyverse with:


And, as always, attach the package by running:


Citing the tidyverse

The most significant update in this version is a new vignette, “Welcome to the Tidyverse”, which is a mirror of the recently-released paper of the same name in the Journal of Open Source Software. The (long) list of authors includes all members of the tidyverse organisation and its component packages, and is now the canonical way to cite tidyverse packages.

When to cite the tidyverse

If you’re in a position where you can easily cite every package that materially contributed to your analysis, you should totally do it. But it is often hard because many packages don’t have accompanying papers, and many journals still haven’t got the memo that software is an important research artifact. Alternatively, you may be publishing in a venue with very tight page constraints and you simply don’t have the room to cite every package. For a more comprehensive discussion of best practices regarding citing software, see Software Citation Principles by Arfon Smith, Daniel Katz, Kyle Niemeyer, and The FORCE11 Software Citation Working Group.1

We generally recommend citing the tidyverse paper instead of citing individual packages. This is less work, making it more likely that people will do it, and helps concentrate the citations across the whole tidyverse into a single place, which makes it easier to show the academic merit of our work. Of course, you’re still free to cite individual tidyverse packages if you feel like they have been particularly important for your analysis, but you shouldn’t feel obliged.

How to cite the tidyverse

The R citation() function makes it easy to cite R and R packages in publications. The latest version of the tidyverse package has the citation built in:

#>   Wickham et al., (2019). Welcome to the tidyverse. Journal of Open
#>   Source Software, 4(43), 1686, https://doi.org/10.21105/joss.01686
#> A BibTeX entry for LaTeX users is
#>   @Article{,
#>     title = {Welcome to the {tidyverse}},
#>     author = {Hadley Wickham and Mara Averick and Jennifer Bryan and Winston Chang and Lucy D'Agostino McGowan and Romain François and Garrett Grolemund and Alex Hayes and Lionel Henry and Jim Hester and Max Kuhn and Thomas Lin Pedersen and Evan Miller and Stephan Milton Bache and Kirill Müller and Jeroen Ooms and David Robinson and Dana Paige Seidel and Vitalie Spinu and Kohske Takahashi and Davis Vaughan and Claus Wilke and Kara Woo and Hiroaki Yutani},
#>     year = {2019},
#>     journal = {Journal of Open Source Software},
#>     volume = {4},
#>     number = {43},
#>     pages = {1686},
#>     doi = {10.21105/joss.01686},
#>   }

Since the tidyverse wouldn’t be possible without R, we strongly recommend that you also cite R:

#> To cite R in publications use:
#>   R Core Team (2019). R: A language and environment for statistical
#>   computing. R Foundation for Statistical Computing, Vienna, Austria.
#>   URL https://www.R-project.org/.
#> A BibTeX entry for LaTeX users is
#>   @Manual{,
#>     title = {R: A Language and Environment for Statistical Computing},
#>     author = {{R Core Team}},
#>     organization = {R Foundation for Statistical Computing},
#>     address = {Vienna, Austria},
#>     year = {2019},
#>     url = {https://www.R-project.org/},
#>   }
#> We have invested a lot of time and effort in creating R, please cite it
#> when using it for data analysis. See also 'citation("pkgname")' for
#> citing R packages.


A huge thank you to the paper’s reviewers, Laura DeCicco and Jeff Hanson, and journal editor, Karthik Ram, who improved the quality of the paper immensely.

We’re also grateful to the 89 people who contributed to this release: @andrewheiss, @arcole, @arfon, @Armos05, @arne1921KF, @batpigandme, @BenoitLondon, @bschneidr, @cawoodjm, @christa88, @coatless, @cryptic0, @cwickham, @d8aninja, @daltonhance, @dan-reznik, @danhalligan, @DataXujing, @DavoOZ, @dchiu911, @dhslone, @Fredo-XVII, @gaborcsardi, @genewch, @grayskripko, @gvwilson, @gwd999, @hadley, @hammer, @harrismcgehee, @ijlyttle, @jennybc, @jeroen, @jflynn264, @jimhester, @jnolis, @JoeFernando, @JoFAM, @jonocarroll, @josegonzalez, @jrosen48, @jtelleria, @jzadra, @karawoo, @karthik, @kent37, @kevinushey, @kevinykuo, @krlmlr, @ljmills, @malcolmbarrett, @maptracker, @martinamorris, @martinjhnhadley, @MartinMSPedersen, @mattsgithub, @maurolepore, @mfherman, @mgsosna, @mikeyEcology, @mloop, @moodymudskipper, @msberends, @njtierney, @osmelmillan, @pgensler, @PoGibas, @psychelzh, @rkalescky, @rmcd1024, @romainfrancois, @rsheppar, @sampath2510, @Selvamjn, @SinfantiHU, @steenharsted, @stefvanbuuren, @steveharoz, @sulgik, @talban14, @thanosgatos, @tmalsburg, @toouggy, @topepo, @tsufz, @willbowditch, @XiangyunHuang, @yatharth, and @yutannihilation.

  1. Smith AM, Katz DS, Niemeyer KE, FORCE11 Software Citation Working Group. (2016) Software Citation Principles. PeerJ Computer Science 2:e86. doi: 10.7717/peerj-cs.86. [return]
Upcoming events
Miami, FL
December 16 – 18, 2019
Improve your tool building skills with this small hands-on workshop on a boat. All profits go to support the mission of the field school.
San Francisco, CA
January 27 – 30, 2020
rstudio::conf 2020 covers all things RStudio, including workshops to teach you the tidyverse, and talks to show you the latest and greatest features.