Michael Chirico

Yes, I think we're about due...

I don't have any issue with a lint roller as the baseline, but that one does not look very good to me.

(by way of context for the flurry of activity, I'm just taking over as maintainer for a repo using {pkgdown} and trying to understand how to integrate updating the release...

> One thing we should definitely copy is the (IIRC relatively new ability) to customise the error message: just for posterity, yes, this was part of R 4.0.0. and just...

{sf} owns the error message, but {ggplot2} owns the map data & I would guess could be responsible for knowing where it comes from & thus what drivers are needed...

I can point to the line causing it: https://github.com/tidyverse/ggplot2/blob/e0d54f6d2be6452bbab61a5018abc231a3172ca6/tests/testthat/test-coord_sf.R#L290 But it will be hard to offer a reprex I'm afraid, sorry :\

I'll have to return to this when I'm off leave in May

``` sf::sf_extSoftVersion() # GEOS GDAL proj.4 GDAL_with_GEOS USE_PROJ_H PROJ # "3.5.0" "3.6.0dev-7f16b09a89" "7.0.0" "true" "false" "7.0.0" ```

I'll report back when it's updated but that may take years :)

I don't think a code fix is needed, but a NEWS entry citing this as a potential breaking change still makes sense to me.