env_unlock() will be removed from rlang

[lionel-]

Hello, just a heads up that we'll remove env_unlock() from rlang in a future version (undetermined timeline as of yet) because it's implemented using non-API calls that CRAN has started to lint. Could you try and find another approach please?

[cboettig]

@lionel- Thanks for the heads up. Do you have a better suggestion then for how to deal with the namespace conflict that is created by cli ? The current use of env_unlock() in this package was provided by @gaborcsardi to address the conflict between competing classes of the same name, #251 (comment)

[gaborcsardi]

The root of the issue was fixed in R 4.2.0, so you should not need this workaround any more.

[cboettig]

perfect, thanks @gaborcsardi !

[hlapp]

@cboettig looks like you addressed this in f94903a but there is no PR and the build fails. Would you mind if I reopen this and we create a PR for documentation?

[cboettig]

@hlapp yes thanks, I was sloppy on that!

Regarding the builds, it's probably time to update the workflow script as well, which can be done with usethis::use_github_actions()