rlang breaking changes

• v0.4.11 \u2192 v1.0.0breaking

  `abort()` now displays errors as fully bulleted lists. Error headers are displayed with a `!` prefix. See <https://rlang.r-lib.org/reference/topic-condition-customisation.html> to customise the display of error messages.

• v0.4.11 \u2192 v1.0.0breaking

  `abort()` now displays a full chain of messages when errors are chained with the `parent` argument. Following this change, you should update dplyr to version 1.0.8 to get proper error messages.

• v0.4.11 \u2192 v1.0.0breaking

  `abort()` now displays function calls in which a message originated by default. We have refrained from showing these calls until now to avoid confusing messages when an error is thrown from a helper function that isn't relevant to users. To help with these cases, `abort()` now takes a `call` argument that you can set to `caller_env()` or `parent.frame()` when used in a helper function. The function call corresponding to this environment is retrieved and stored in the condition.

• v0.4.11 \u2192 v1.0.0breaking

  cli formatting is now supported. Use `cli::cli_abort()` to get advanced formatting of error messages, including indented bulleted lists. See <https://rlang.r-lib.org/reference/topic-condition-formatting.html>.

• v0.4.11 \u2192 v1.0.0breaking

  New `try_fetch()` function for error handling. We recommend to use it for chaining errors. It mostly works like `tryCatch()` with a few important differences.

• v0.4.8 \u2192 v0.4.9breaking

  Dropped support for the R 3.2 series.

Get this data programmatically \u2014 free, no authentication.